Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update / Pulling image results in "no space left on device" #5

Open
CozMedic opened this issue Mar 12, 2024 · 3 comments
Open

Update / Pulling image results in "no space left on device" #5

CozMedic opened this issue Mar 12, 2024 · 3 comments

Comments

@CozMedic
Copy link

CozMedic commented Mar 12, 2024

I was having unifi-specific issues and in troubleshooting I thought to pull down the latest container. I came back here to follow your instructions using updatedocker.sh but I received the following in the terminal:

fc6a701a0672: Pull complete
4e067bf34ebb: Verifying Checksum
4e067bf34ebb: Download complete
failed to register layer: Error processing tar file(exit status 1): write /usr/lib/unifi/webapps/ROOT/app-unifi/setup/static/js/vendor.8d209f3cb064f398f99e.js.br: no space left on device
Pulling Container
stopping unifi's...
unifi
removing unifi's container
unifi
Creating unifi ... error

At the end all I was left with was:

ERROR: for unifi  Cannot start service unifi: network unifi_default not found

ERROR: for unifi  Cannot start service unifi: network unifi_default not found
ERROR: Encountered errors while bringing up the project.
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
Press any key to continue:

This is on a Firewalla Gold+

@CozMedic
Copy link
Author

Hitting continue, I pruned leftover images and ran the installation script again. The checks worked as expected and it used the newer image. Not sure if I really ran out of space and if so, if there's a way to implement a check that will better prepare for the scenario. I only have this container on my Gold+ and seemingly had two "stale" images (after pulling the latest).

pi@Firewalla:~/.firewalla/run/docker (Firewalla) $ curl -s -L -C- "https://raw.githubusercontent.com/mbierman/unifi-installer-for-Firewalla/main/unifi_docker_install.sh?$(date +%s)" | cat <(cat <(bash))

✅ unifi directory exists.

✅ unifi run directory exists.

✅ unifi yaml created.
CONTAINER ID   IMAGE                       COMMAND                  CREATED         STATUS                   PORTS
                                              NAMES
e31bb9b14916   jacobalberty/unifi:latest   "/usr/local/bin/dock…"   4 minutes ago   Up 4 minutes (healthy)   6789/tcp, 8080/tcp, 8443/tcp, 8843/tcp, 3478/udp, 10001/udp, 8880/tcp   unifi
Starting docker (this can take ~ one minute)
✅ unifi has started
configuring networks...

✅ Networks configured

✅ unifi network settings saved.

✅ Network service restarted...
Restarting docker unifi

Starting the container, please wait....

Starting docker (this can take ~ one minute)
✅ unifi has started
Done!

@mbierman
Copy link
Owner

The error does say no space left on the device. I'm not sure what else can be done. Ideas?

@CozMedic
Copy link
Author

In my case, the sudo $DOCKER image prune line coming before sudo docker-compose up -d would have stopped the issue from occurring, but I'm surprised I ran out of storage since Unifi controller is the only image I run. Have you ran into a similar issue before?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants