this post was submitted on 23 Jun 2024
9 points (100.0% liked)

Docker

1104 readers
1 users here now

founded 1 year ago
MODERATORS
 

I am running Fedora Server with Docker installed, and it has a folder that connects to my NAS via SMB. I will have all of my Docker files (and Compose configs) stored on my NAS, since it has a lot more storage. I am worried that Docker will glitch out and cause a mess, since my NAS starts ~2 minutes later than my server from a reboot. Is there something that I can do to make sure Docker is able to connect to the SMB share safely?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 4 months ago

I would use NFS instead of SMB. you will have all sorts of problems when you use smb, primarily permissions.

Also I wouldn't put all the data on the nas. What containers do you want to run? If you try to run something like nextcloud, you can just map your data directory to your nas. Databases, configfiles and so on aren't that big usually and your application will be a lot faster when those are on your local storage instead of the nas. For actually mapping your containers data to your nas you can just use bind mounts.

For the startup, you can set restart:never in your compose file and start the container with a script after bootup where you out something like 'sleep 120' in the beginning.