Set a Delay on bootup

[[email protected]]

is there a way to delay the startup of the docker engine/containers on system bootup

I have a mounted network SMB share that a few of my dockers use and on a system boot up
the docker engine and dockers load before the smb share is mounted and then of course the dockers

using that share can not see it.  i've gotten in a habbit of just restarting those dockers after power up

and all is well but i'd like to just fix the issue if possible....
 

[Squid]

I've never had a problem with any container using SMB shares.  but, I suppose it is entirely possible.  I would try setting "slave" as the access mode on those path mappings when you edit the container

[itimpi]

3 hours ago, [email protected] said:

is there a way to delay the startup of the docker engine/containers on system bootup

I have a mounted network SMB share that a few of my dockers use and on a system boot up
the docker engine and dockers load before the smb share is mounted and then of course the dockers

using that share can not see it.  i've gotten in a habbit of just restarting those dockers after power up

and all is well but i'd like to just fix the issue if possible....
 

If you go into the Advanced view on Settings->Docker then you can:

• change the startup order using drag-and-drop
• set a delay AFTER starting a container before attempting to start the next one.