andrebrait
Members
-
Joined
-
Last visited
Solutions
-
andrebrait's post in Docker crashing - Docker failed to initialize, socket not available but some containers keep running and other oddities was marked as the answer@JorgeB it turns out it was a failing power supply.
The Corsair SF750 Platinum I was using was probably having a hard time dealing with the bursty loads caused by Docker's recurring maintenance tasks/checks so it ended up happening disproportionally there, but the machine was also turning itself off.
It's been running like a champ since I disabled all power saving features possible to confirm the PSU had issues with low power modes.
-
andrebrait's post in SWITCHING DOCKER DATA ROOT was marked as the answerYes, you should be able to delete them.
If yoh want, you can "test that" by renaming the folder / moving the contents somewhere else, rebooting/restarting docker and seeing if anything changes for you.
But given you're using the image method, you should be able to just delete that folder as it's not being used anymore anyway.
