Submitted 1 week ago by gedaliyah@lemmy.world to selfhosted@lemmy.world
So I recently moved most of my docker storage to a second hard drive, called “storage.” After a system restart, docker is creating a folder called “storage,” forcing the physical drive to be renamed “storage1.” How do I prevent this from happening?
I am using Xubuntu.
It looks like you’re relying on media automounting to access the drive, but this is happening too late for Docker.
I would suggest creating the empty folder and explicitly adding the Mount to /etc/fstab instead. This should mount early enough, and even if it doesn’t it needs an empty folder for the mount point anyway.
Agreed. Needs to be a required mount in fstab. System won’t even start then if the mount fails, docker always has access
Thanks - this was the solution. I’ve updated the post to reflect the solution I used.
It sounds to me like one (or more) of your containers is referencing something on your storage drive, but Docker is loading before your drive gets mounted. When Docker sees that the folder its trying to access doesn’t exist, it creates it, blocking your drive from taking that name.
To fix it, you would need to make sure your storage drive is mounted before Docker starts, how you do that is down to you and your particular setup though.
That’s a good theory. This may be able to be investigated further with systemd-analyze plot > boot.svg
Is Docker starting up and one of the containers mounts a volume to a /storage folder on the host? That could explain it but I’m not super clear on all that’s going on in your system.
Quick test: disable auto start on all your containers and restart and see if it recurs.
I believe that’s exactly what is happening. I just don’t know how to fix it. I could edit the YML files and delete restart: unless-stopped but I want my containers to restart if something goes down unexpectedly
So is the issue that your extra drive mounts to /storage, but that happens after Docker has already started and taken over the directory, so the mount fails? Normally I’d expect it to happen in the other order. Is this a weird race condition?
This might be a good thing to run through with ChatGPT- there are probably ways to delay the Docker container start, but maybe there’s a more significant misconfiguration you can deal with.
walden@sub.wetshaving.social 1 week ago
I’m not an expert, but I think we need more information.
gedaliyah@lemmy.world 1 week ago
I’m even less of an expert lol. What information can I provide to help?
towerful@programming.dev 1 week ago
The commands you used to start the docker containers, or the docker compose contents.
That’s what dictates how much “power” a docker container has