Closed 7imbrook closed 7 years ago
workaround: systemctl restart docker
systemctl restart docker
everything comes back online, but it's an inconvenience
Turns out there's a pattern of ssedev downtime that kills the engine and it's due to network latency during vm backups.
workaround:
systemctl restart docker
everything comes back online, but it's an inconvenience