Your docker folder is full... You need to move the docker folder off your OS drive (it's probably Plex or Emby causing this). You'll need to do the following as root.
1. First, create a folder on one of your data drives somewhere. (mkdir /path/to/folder)
2. service docker stop -- Stops docker service
3. mv /var/lib/docker /path/to/folder -- This moves your docker containers/images to the folder you created in step 1.
4. ln -s /path/to/folder /var/lib/docker -- Creates a symbolic link between the folder you moved your dockers to, and /var/lib/docker (this will keep you from having to reinstall and reconfigure all the dockers you currently have)
5. service docker start -- Starts docker.
Reboot, and you should have docker running as normal and be able to get to the webUI
Alles anzeigen
btw.. i use a litte M.2 card. I have 18gb free. you wrote its better to swap the docker files on a HDD.. but not a folder under mergerfs?!
Do NOT use mergerfs to store dockers or plex config.
Alles anzeigen
crap... this killed more i can post here: maybe there was more broken that just docker.
But not so important.. I just started a new installation..
btw.. i use a litte M.2 card. I have 18gb free. you wrote its better to swap the docker files on a HDD.. but not a folder under mergerfs?!
Those instructions are fine (if you didn't use them on mergerfs... I always forget that's an issue because I don't use it). I've used them multiple times with zero issues (you can google moving docker containers to another drive, and you'll see the same instructions mentioned more than a few times).
Putting the docker files on another drive (you said in the OP that is what was the docker folder filling up your OS drive). If you have a small OS drive, and you're running some of the containers that can have very large metadata folders (Plex and Emby are the biggest culprits).. then it's very easy to fill up a small OS drive.
Search this forum for "OS Drive Full" and you'll see this isn't an uncommon issue when people don't set up docker correctly (or at least don't set it up correctly to account for a small OS drive).
Alles anzeigenYour docker folder is full... You need to move the docker folder off your OS drive (it's probably Plex or Emby causing this). You'll need to do the following as root.
1. First, create a folder on one of your data drives somewhere. (mkdir /path/to/folder)
2. service docker stop -- Stops docker service
3. mv /var/lib/docker /path/to/folder -- This moves your docker containers/images to the folder you created in step 1.
4. ln -s /path/to/folder /var/lib/docker -- Creates a symbolic link between the folder you moved your dockers to, and /var/lib/docker (this will keep you from having to reinstall and reconfigure all the dockers you currently have)
5. service docker start -- Starts docker.
Reboot, and you should have docker running as normal and be able to get to the webUI
Hi, I done exactly what you wrote but after reboot I don't have any container running. In OMV UI, in extras, I can see that any portainer container is running.
Any help? Thanks
EDIT: the mv of the docker dir into the new dir, 'caused the writing into a sub-dir, so after the restart of the service (and the reboot) docker re-created its ambient... now I moved from the sub-dir to the up-level and restarted. Just some minutes for the reboot and I'll see if all is ok.
CONFIRMED
Hi, I done exactly what you wrote but after reboot I don't have any container running. In OMV UI, in extras, I can see that any portainer container is running.
Any help? Thanks
It should still work (I'm gussing you did not create the link properly). Howver, that is extremely old and hasn't really needed to be done that way in some time. Depending on your version of OMV the smarter thing to do would just be to move your docker folder as it says, and then just point the docker plugin at the new location of the folder.
.
If you look in the guide forum, there's a more recent instruction on how to deal w/ a full OS drive.
OK, thanks. Now is working again.
I'll try to find out the new instructions for my OMV 6.0.
Thanks again
Be carfull when moving existing containers. The volume pathes are part of a containers config (see docker inspect <container>).
If you do not recreate the container it will still point to the old directory. It is better to destroy* all containers before moving the docker root.
* destroying means docker-compose down
Be carfull when moving existing containers. The volume pathes are part of a containers config (see docker inspect <container>).
If you do not recreate the container it will still point to the old directory. It is better to destroy* all containers before moving the docker root.
* destroying means docker-compose down
At least my experience doing this with more recent versions of the docker plugin... Stopping docker, move /var/lib/docker off of root to /some-uuid/docker.. Then go to the docker-plugin and change the path to /some-uuid/docker, and restart docker...
It will be like nothing happened.
If it works, it is good, but check here:
root@omv:~# docker inspect portainer
[
{
"Id": "b2c87311458700c8b4d6f22693aba4d6b9e823fa80ea67c94a967f45efa2cc1d",
...
"ResolvConfPath": "/srv/dev-disk-by-label-docker/docker-root/containers/b2c87311458700c8b4d6f22693aba4d6b9e823fa80ea67c94a967f45efa2cc1d/resolv.conf",
"HostnamePath": "/srv/dev-disk-by-label-docker/docker-root/containers/b2c87311458700c8b4d6f22693aba4d6b9e823fa80ea67c94a967f45efa2cc1d/hostname",
"HostsPath": "/srv/dev-disk-by-label-docker/docker-root/containers/b2c87311458700c8b4d6f22693aba4d6b9e823fa80ea67c94a967f45efa2cc1d/hosts",
"LogPath": "/srv/dev-disk-by-label-docker/docker-root/containers/b2c87311458700c8b4d6f22693aba4d6b9e823fa80ea67c94a967f45efa2cc1d/b2c87311458700c8b4d6f22693aba4d6b9e823fa80ea67c94a967f45efa2cc1d-json.log",
...
"GraphDriver": {
"Data": {
"LowerDir": "/srv/dev-disk-by-label-docker/docker-root/overlay2/2203871ead73d2e82f0fbc5b4bdc257819a215126dc0eb8c6def8cb9b8ad72b2-init/diff:/srv/dev-disk-by-label-docker/docker-root/overlay2/8607812621fe0f333b0a30ee333c11905946b7802f08aa16504f766bce9934f1/diff:/srv/dev-disk-by-label-docker/docker-root/overlay2/b6bed523581b7356cdadc271e95b1659f20b735a56140711e66d04fa2cb3a95f/diff:/srv/dev-disk-by-label-docker/docker-root/overlay2/9467016b2426ed8df3f9dfc2675c9773a560f37378936ddd3e2cab4bbbd24451/diff",
"MergedDir": "/srv/dev-disk-by-label-docker/docker-root/overlay2/2203871ead73d2e82f0fbc5b4bdc257819a215126dc0eb8c6def8cb9b8ad72b2/merged",
"UpperDir": "/srv/dev-disk-by-label-docker/docker-root/overlay2/2203871ead73d2e82f0fbc5b4bdc257819a215126dc0eb8c6def8cb9b8ad72b2/diff",
"WorkDir": "/srv/dev-disk-by-label-docker/docker-root/overlay2/2203871ead73d2e82f0fbc5b4bdc257819a215126dc0eb8c6def8cb9b8ad72b2/work"
},
"Name": "overlay2"
},/srv/dev-disk-by-label-docker/docker-root being my docker root.
Have to try on a test machine if this is updated if I restart docker with a different docker-root.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!