I did the upgrade to 7.0 and found that the docker service started after the reboot, but then shut down. I rebooted again (and again) and the docker service won't start. In Settings > Docker it shows Yes (Enable Docker), but it shows the "Docker Service failed to start" when viewing the Docker tab. I set it to No > Apply > Yes > Apply with no change.

Attached is my Diagnostic file. Any help would be appreciated.

tower-diagnostics-20250124-1738.zip

Server ran out of RAM, looks like container related, reboot should resolve the docker start issue, but if it happens again, you will need to investigate to try and find the culprit container.

Thanks for the response.
I've rebooted again (and again...) with no change. Docker won't start. And server becomes unreachable after several hours of 'sitting'. No ping. After reboot(s) it will ping and boot to an interface without docker running - then stop responding again hours later.

Is there a way to investigate which container is the culprit with the docker not starting?

 

Edited January 25, 20251 yr by lookout

19 hours ago, lookout said:

I've rebooted again (and again...) with no change. Docker won't start.

Post new diags after a reboot.

The post above with the diag file was after multiple reboots. As an update though: One of the reboots since let me run long enough to do a downgrade to 6.x. That worked! I'm running fine now after moving back from 7.x to 6.x. I'm going to stay here for awhile.

Edited January 29, 20251 yr by lookout

If it helps, I had the exact same issue and followed this which fixed it

 

 

Thanks @Shadoxity. I'm going to do this anyway - I'd love to insure that I don't run out of space. I have not gotten the error though... but it seems like a good idea.

I'm ok since downgrading.