cTron

Found it. Learning is fun...

Interesting place to put that. I did that and turned off all auto starts. I still have the same 5 containers autostarting anyway.

Is that done another way than just unlocking them and dragging them around? Because that didn't fix anything.

I have removed FolderView and restarted.

Na. I got that. Both the first and second can start. That's fine. I need it to wait after the second one until the Synology has had time to start and be mounted. The issue is that other ones down the line are ignoring all that and starting anyway. And that the Synology mount doesn't seem to happen first. Extra fun fact. If I turn off the auto start the same docker containers still start anyway. Could this be related to FolderVIew2 which I got rid of to try to fix these issues?

I have all my data on my Synology. I recently started using Unraid to run all of my programs instead of Windows so Unraid mounts the Synology through the SMB that Windows was using. I use 300s delay on mounting the Synology so it can start up before Unraid tries to mount it. Homarr and the Satisfactory server can load straight away. So I was using the Satisfactory container to put in a wait to clear the Synology mount time. Some of this is working great and stepping through and loading them. But 4 ignore the delays and just start as soon as Unraid starts. And those are the ones that really need to be delayed because they target the Synology. In the screenshot you can see the first two starting at the same time at the start with a (currently) 600 wait but the 3rd one loads at the same time anyway. Then it's working correctly and stepping through down to those last 3 that started with the first ones. So it's kind of two issues. The SMB mount doesn't seem to be starting before/at the same time as the docker containers. And the docker containers aren't following the order they are given.

I'm hoping someone can help me out here. I'm having a couple issues. Problem 1. My docker containers aren't loading in the order they are supposed to. Several of the docker containers down the list load instantly (Radarr, etc.). Currently I have it set with a 300s wait on Unassigned Devices to mount SMB for the Synology to start. Assuming Docker starts loading at the same time I set Homarr and Satisfactory to load and then wait 600s before starting to load media stuff that targets the NAS. It also has this on pretty much ever docker container. Jan 11 11:30:00 kernel: docker0: port 7(vethe6df6f2) entered blocking state Jan 11 11:30:00 kernel: docker0: port 7(vethe6df6f2) entered disabled state Jan 11 11:30:00 kernel: vethe6df6f2: entered allmulticast mode Jan 11 11:30:00 kernel: vethe6df6f2: entered promiscuous mode Problem 2. SMB mounting is failing with SMB 3.1.1 and 3.0 and using 2.0. It's a Synology running the newest DSM. kernel: CIFS: VFS: cifs_mount failed w/return code = -95 Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers