My Docker service stopped because my downloads share filled up the cache pool completely. I’ve already started the Mover and now have ~100GB free on the cache (and it’s still increasing), but Docker still won’t start.

Is there a way to get Docker to start again without rebooting the server?
Do I need to restart a specific service or clear a lock file?

Any guidance would be appreciated.

If the issue is resolved, restarting the Docker service should do it, if it doesn't, post the diagnostics.

30 minutes ago, JorgeB said:

If the issue is resolved, restarting the Docker service should do it, if it doesn't, post the diagnostics.

diagnostics-20251209-1048.zip

Array is not started. New diags after array start, please.

58 minutes ago, JorgeB said:

Array is not started. New diags after array start, please.

diagnostics-20251209-1247.zip

According to the diags, docker service appears to be running.

Yes, it’s running now. I wasn’t sure when someone would be available to look at the logs, so I restarted the server. This issue has been happening for a while, and I was hoping to understand whether it’s normal or if there’s a technical reason behind it.

Whenever the cache fills and I move items out of it via mover, Docker still won’t re-enable via the GUI or terminal until I completely reboot the server. I’m trying to understand why Docker doesn’t start again once space is freed, and why a full reboot is required to restore functionality.

4 hours ago, drtechnolust said:

Whenever the cache fills

You should set a Minimum Free Space value on the ‘cache’ pool to avoid it filling up in the first place

12 minutes ago, itimpi said:

You should set a Minimum Free Space value on the ‘cache’ pool to avoid it filling up in the first place

Ah yes… the Minimum Free Space setting in on the 'Cache' pool which is set to 0. The thing I absolutely should have set years ago, it was literally there in plain sight… and absolutely didn’t set it. Consider this mystery solved and my pride slightly wounded. 🤣 Thanks!