Just happened again after a brief stop and power cycle. This time Docker did restart the container multiple times, but of course it didn’t fix anything since the issue seems to be on the supervisor side and not the container’s fault. Got 2 503s in a row, followed by many 404s (>10) before I manually rebooted the device.
For reference, it happened around 15:16 UTC in case anyone takes a look at the journal.