OMFG I just spent an hour learning more dumb stuff about Docker, kernels and old Digital Ocean machines…
I used the power of herb and wine to fix it, so I don’t feel like writing it up at the moment. But it happened.
Oh yeah, links:
- docker: Error response from daemon | by Dirk Avery | Medium
- CVE - CVE-2019-5736
- Search results for '"write init-p: broken pipe"": unknown' - Docker Forums. - useless search
- Docker: copying bootstrap data to pipe caused "write init-p: broken pipe" - support - Discourse Meta
- Latest package on Ubuntu trusty/14.04 (18.06.2~ce~3-0~ubuntu) is broken with runc · Issue #591 · docker/for-linux · GitHub
- server - Still on previous 4.15 kernel after apt upgrade to 18.04.2 - Ask Ubuntu
- https://wiki.ubuntu.com/Kernel/LTSEnablementStack
- How to Boot into a Specific Kernel Version :: DigitalOcean Product Documentation
- How to Switch to Internal Kernel Management with the DigitalOcean GrubLoader Kernel :: DigitalOcean Product Documentation
Basically, Docker broke and then Ubuntu broke and then my brain broke and then Digital Ocean actually broke it except it was because talkgroup is a really old site on the same VPS the whole time and I am kinda happy to have such strange issues due to creating a nice space and legacy online…