archedraft Posted August 1, 2015 Share Posted August 1, 2015 My docker 10GB .img just filled all the way up today. Is there a certain command to give it more space? Link to comment
Squid Posted August 2, 2015 Share Posted August 2, 2015 Settings / Docker Stop Docker Delete the existing image file Recreate the image file with a greater size, and enable docker Add your containers again via "Add Container", and select all of your "my*" containers you were using. After all the downloads happen again, it will be like nothing happened. Link to comment
archedraft Posted August 2, 2015 Author Share Posted August 2, 2015 Awesome, I was guessing that was the case. Thanks for your reply. As it turned out, the real reason was the SSD ran out of space not the docker.img. I just setup a new windows 10 VM and got a little carried away installing new things. Then all of the sudden I couldn't access some of my dockers. Ended up moving some stuff off the SSD and problem solved. Link to comment
aptalca Posted August 3, 2015 Share Posted August 3, 2015 Do you really have to delete the img file and reinstall all the dockers? It's been a while, but I kinda remember just stopping docker, changing the img size and restarting it. I think unRaid just added more blank bits using the dd command and expands the file. I don't think I had to reinstall anything. But like I said, that was a while back and my memory ain't what it used to be :-) Link to comment
Squid Posted August 3, 2015 Share Posted August 3, 2015 Do you really have to delete the img file and reinstall all the dockers? It's been a while, but I kinda remember just stopping docker, changing the img size and restarting it. I think unRaid just added more blank bits using the dd command and expands the file. I don't think I had to reinstall anything. But like I said, that was a while back and my memory ain't what it used to be :-) You could be correct. Never had a reason to go beyond 20G, so its just how I would have guessed that it would work. Link to comment
aptalca Posted August 3, 2015 Share Posted August 3, 2015 So you're not gonna go to 21G just for the love of science and experimentation? And what about shrinking the img? I think these questions demand an answer!!! I elect sparklyballs for the testing Link to comment
Squid Posted August 3, 2015 Share Posted August 3, 2015 ok... I took one for the team. Stop docker. Increase the size. Restart docker. Done Not in the mood however to decrease the size. Sparkly can handle it. Link to comment
archedraft Posted August 3, 2015 Author Share Posted August 3, 2015 Stop docker. Increase the size. Restart docker. Done Fancy, wait... flared pinky fancy. UnRAID has definitely come a long! Link to comment
BRiT Posted August 3, 2015 Share Posted August 3, 2015 You still want to go through the process of deleting it all since you dont know what possible corruptions were caused from hitting the absolute limit. Link to comment
Kryspy Posted August 4, 2015 Share Posted August 4, 2015 I was under the impression previously we could expand but not shrink a docker image file without deleting it first?!? Kryspy Link to comment
smdion Posted August 4, 2015 Share Posted August 4, 2015 I was under the impression previously we could expand but not shrink a docker image file without deleting it first?!? Kryspy this is truth Link to comment
CHBMB Posted August 4, 2015 Share Posted August 4, 2015 I've hit the limit twice and ended up with a corrupted docker image. Should be ok with the 30G I've allocated now.. Link to comment
archedraft Posted August 4, 2015 Author Share Posted August 4, 2015 30G I've allocated now.. I think you're having way to much fun with docker! Link to comment
CHBMB Posted August 4, 2015 Share Posted August 4, 2015 30G I've allocated now.. I think you're having way to much fun with docker! Shouldn't have to increase it again for a while Label: none uuid: 1b92ba03-511e-46a3-944d-a0695834ce69 Total devices 1 FS bytes used 20.20GiB devid 1 size 30.00GiB used 24.04GiB path /dev/loop0 btrfs-progs v4.1 Link to comment
scytherbladez Posted August 4, 2015 Share Posted August 4, 2015 This seems an appropriate place to ask the following... What is the best way to manage the docker's increasing size? My docker size has been increasing. I do update dockers when available, does this mean garbage is being left behind every upgrade? If the above is true, is the only way to manage the increasing size to remove the docker container+image, and re-add? (other than increasing the docker size itself). Thanks Link to comment
BRiT Posted August 5, 2015 Share Posted August 5, 2015 This seems an appropriate place to ask the following... What is the best way to manage the docker's increasing size? My docker size has been increasing. I do update dockers when available, does this mean garbage is being left behind every upgrade? If the above is true, is the only way to manage the increasing size to remove the docker container+image, and re-add? (other than increasing the docker size itself). Thanks To manage docker size properly: 1) Do not update dockers 2) Do not run auto-updating dockers 3) Do not install/uninstall/install/uninstall dockers 4) Periodically scrub your docker using the UI Settings/DockerSettings page My docker size is 654 megs in use after 5.5 weeks of use, when initial base size after first creations was around 645 megs. I run the following 3 dockers: EggDrop, NzbGet, and a torrent program. For those who update too frequently or use auto-updating programs the following step is required: 5) Nuke From Orbit periodically to restart back to pristine condition. Link to comment
scytherbladez Posted August 5, 2015 Share Posted August 5, 2015 That advise is even worse than I expected. I just came across your docker maintenance thread http://lime-technology.com/forum/index.php?topic=37407.0 here, too. What's LT official response been on this? Seems to be a pretty big flaw Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.