-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
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).
|
The error does say no space left on the device. I'm not sure what else can be done. Ideas? |
In my case, the |
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:
At the end all I was left with was:
This is on a Firewalla Gold+
The text was updated successfully, but these errors were encountered: