[Bug] CIFS share not mounting on first boot only about docker-filebot

[jlesage]

Is the container automatically started at boot ? Are you sure that unRAID mounted the SMB share before starting the container?
Looks like that at the time the container started, the SMB share was not mounted yet.

[bearattack11]

Yes, the container is automatically started on boot.

I'm not sure if that the SMB share is mounted before the container, but I have the jlesage/docker-mkvtoolnix container installed and that always flawlessly mounts the SMB shares every time.

I've tried to re-order the container startup sequence so that FileBot starts last (I have about 7 containers total), but that seems to have no impact. Again, MKVToolNix still mounts its SMB share with no issue.

[jlesage]

I don't know why you don't see the same issue with other containers, but the container itself has no control over this SMB mount (i.e. it's not the container that mounts the folder).

You can see the following post that explains how to start a container after a share is mounted: https://forums.unraid.net/topic/142625-wait-first-container-start/

[bearattack11]

That script definitely did the trick... I'm not sure why this isn't happening with my other containers (all using SMB mounts too) but I guess for now I will thank good luck.

Thank you!