Docker containers ignoring auto-start after unclean shutdown

[oliver]

I had several kernel panics and unclean shutdowns, after recovery, some of my docker containers aren't respecting the auto-start flag.  I have everything turned off but some of them still start with array start. 

 

I tried flipping the flags, editing the containers to generate a new one but they keep starting with the array when they shouldn't.  

 

How is this flag controlled (docker.img?) and how can I view/edit it?

[JonathanM]

AFAIK an unclean shutdown detected startup doesn't honor auto starts on purpose, reasoning is probably so that a possible boot loop will not happen.

 

Does everything work properly if the prior shutdown completed successfully?

[oliver]

12 hours ago, JonathanM said:

AFAIK an unclean shutdown detected startup doesn't honor auto starts on purpose, reasoning is probably so that a possible boot loop will not happen.

 

Does everything work properly if the prior shutdown completed successfully?

 

Unfortunately not, even with a clean shutdown, the auto-start settings are no longer honored for some of the containers.  

[JonathanM]

Diagnostics might hold some clues.

[oliver]

nas-diagnostics-20240510-1844.zip

 

I've attached some older diagnostics when I was troubleshooting the crashes earlier.  Logs just appear to show the array starting as normal.  In this bootup, all docker containers are set for autostart:off but you can see some starting normally.