

I had to physically log into the server (I am not using a VPS) and docker compose -f ... down
the container in order for it to be solved. After a downgrade of nextcloud it was solved and the next upgrade I did, didn’t experience the same issue. I ended up ditching nextcloud anyway because after an update ~8-12 months ago, the login page has never loaded since, so it can’t be used. I found out I rarely used it anyway.
Not to discredit what he did because he was probably one of the biggest impact decisions taken ever, he is definitely a great man and he deserves every ounce of credit, but he did not defy orders. They received no orders whatsoever, and the captain just assumed a war had broken out. They were too deep to receive orders at all. He refused to give his permission which was “legally” (military law-wise?) needed to launch the nukes. From your own link (also he wasn’t a commander at the time):
So it doesn’t really apply. It is more one of 3 commanding officers that had a big disagreement and one of them refused to let the others give the order.