This morning I noticed that several open GitHub PRs failed to build, halfway expected a weird API breakage. But when I decided to look into it, the build runner couldn’t connect to the Maven Repository:

Caused by: java.io.IOException: Unexpected response code for https://maven.alphadev.net/releases/de/sipgate/dachlatten-io/0.0.101/dachlatten-io-0.0.101.pom.sha512. Expected: 200, actual: 502

Quick check in the Browser, and I was greeted with the Reverse Proxy landing page of the host, so the service itself was actually down.

After logging into the Host, it transpired that the host was automatically restarted for an unattended update, but the Docker daemon was somehow corrupted and never came back up again.

The offered “reparation” seemingly entailed reinstalling Docker and restarting with the old data dir, which thankfully wasn’t actually corrupted.

Not exactly sure what had happened here. Will keep an eye out for recurring occurrences. Thankfully the data dir is regularly backed up.