I have a dockerized environment. The development environment sets up and tears down the database. The whole thing runs in a VM, that worked just fine a month ago.
I started the VM after a month (I literally didn't touch it since last run), killed and removed and stopped containers. Pruned volumes. The database container just won't start.
Nothing was upgraded.
I reboot the VM, the system works.
Now tell me a) how this is possible b) how am I not supposed to be extremely angry.
buherator /
npub1n3…djee0
2023-12-10 09:30:56
Author Public Key
npub1n3p6whdpmt9k8rxzcmvrs053utg662lfrgdxh7dl9t04ff8sdk7qqdjee0Published at
2023-12-10 09:30:56Event JSON
{
"id": "4d175a57c97e787e8d24b31ae660b98a4f0ff1e354005a700356f35d2c721225",
"pubkey": "9c43a75da1dacb638cc2c6d8383e91e2d1ad2be91a1a6bf9bf2adf54a4f06dbc",
"created_at": 1702200656,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.place/objects/3abf4915-3df2-4d2a-8191-0a0dfec00262",
"activitypub"
]
],
"content": "I have a dockerized environment. The development environment sets up and tears down the database. The whole thing runs in a VM, that worked just fine a month ago. \n\nI started the VM after a month (I literally didn't touch it since last run), killed and removed and stopped containers. Pruned volumes. The database container just won't start. \n\nNothing was upgraded. \n\nI reboot the VM, the system works. \n\nNow tell me a) how this is possible b) how am I not supposed to be extremely angry.",
"sig": "6266b955ebf87a1c4e0a5e11583fdb36b9845719ab78b60b8168e2111219f3894e679ddc1fcd9d506b09012b41d366f7aa4572da04f5105098ac00e430459e73"
}