[dockers / stopping array]

another test.  I needed to reboot the entire server.  8 of 10 docker containers are set to auto-start.   Upon reboot, all my containers were down.  None would start until i disabled the docker service and then re-enabled it.  As soon as I do this, the containers that were set to auto start started right up automatically.   This is the same issue as the above, just throwing the reboot into the mix.

Please help me trouble shoot this; some services are important (like the pihole container)

[dockers / stopping array]

Hi - most of my containers are set to auto start but they will fail until I disable the docker service (settings > dockers > enable dockers)  and then re-enable it.   Is there some debugging you'd like me to enable?

[dockers / stopping array]

Hi folks.  Thanks for clearing up my clumsy wording.

Running 6.6.6 and using docker with multiple containers.  Steps to reproduce.

 

1) shutdown containers

2) stop array

3) start array

4) attempt to start containers

Most of my containers are set to auto start. 

 

Unraid will show all my existing containers.  However when I attempt to start them unraid will complain no such image is available.  To work around this, I go to settings > docker. Disable the docker feature, apply, then re-enable the docker feature.   Once I perform this action I am able to successfully launch the containers. 

[dockers / stopping array]

syslog around 19:08 today

[dockers / stopping array]

been a couple hours since i did the above steps.  If this doesn't work i'll repost.   let me know

cybertron-diagnostics-20181226-2126.zip