This is a non safe for work, as in lewd, instance.
It’s safe to assume that anything you see here will be lewd.
Just letting you know. If you view the content and then pull a surprised pikachu when you see big anime tiddies, Judy Hopps getting railed or some furry vore… Then it’s on you.
Should this popup continue to show up, you may want to enable cookies or disable privacy focused addons on your browser, I assure you we won’t track our user.
Should that fail, some users claim they got rid of it by hammering the ok button.
We’ve completely transitioned from docker to podman where I work. The only pain point was podman compose being immature compared to docker compose, but turns out you can run docker compose with podman using the podman socket easily.
I gave podman compose a fresh try just the other day and was happy to see that it “just worked”.
I’m personally pissed about aardvark-dns, which provides DNS for podman. The version that is still in Debian Stable sets a TTL of 24h on A record responses. This caused my entire service network to be disrupted whenever a pod restarted. The default behavior for similar resolvers is to set a TTL of 0. It’s like people who maintain it take it as an opportunity to rewrite existing solutions in Rust and implement all the bugs they can. Sometimes feels like someone just thought it would be a fun summer break project to implement DNS or network security.
I think you wrote it back ways: transitioned from docker to podman?
Yeah podman should use quadlets, not compose, but still works just fine with docker compose and the podman socket!
Oops. Thanks for the correction.
I hadn’t heard of quadlets. I’ll have to give them a look.