Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Transitioning from Docker to Podman

developers.redhat.com

Post reply on HN
Print view View original

201–210 of 278 posts

Re: Transitioning from Docker to Podman

#201

Post by babarock »

Cu3PO42 wrote: post #34

I love the idea of Podman being daemonless and (potentially) rootless. Regardless of the presence of security flaws in dockerd, the Podman architecture just feels cleaner. And the CLI compatibility is great. Until it isn't. At work we switched to Podman for a small deployment because Docker didn't yet work with cgroupsv2 and many hours were spent debugging Podman-specific issues. In the end switching to cgroupsv1 wou…

Genuinely curious what issues you came across. Any chance you documented them somewhere?

Re: Transitioning from Docker to Podman

#202

Post by torvald »

IceWreck wrote: post #200

For anyone not using Podman just because lack of docker compose like functionality, there are multiple alternatives. * Podman's official stance is to use Kubernetes YAML. The provide tools to generate this as well as convert docker-compose to kubeyaml * podman-compose is not official, but it works well. you have to note that its not 100% compatible with dc but a lot of dc files run out of the box without modification…

I pray for a Hashicorp Nomad driver as well!

Re: Transitioning from Docker to Podman

#203

Post by Cu3PO42 »

babarock wrote: post #201
Cu3PO42 wrote: post #34

I love the idea of Podman being daemonless and (potentially) rootless. Regardless of the presence of security flaws in dockerd, the Podman architecture just feels cleaner. And the CLI compatibility is great. Until it isn't. At work we switched to Podman for a small deployment because Docker didn't yet work with cgroupsv2 and many hours were spent debugging Podman-specific issues. In the end switching to cgroupsv1 wou…

Genuinely curious what issues you came across. Any chance you documented them somewhere?

I'm afraid I didn't and I cannot really recall, but many were related to networking. I think one was that I couldn't have two containers on the same network listen to the same port, another one was related to Podman not playing nice with nftables, but the specifics elude me.

EDIT: Upon further reflection, I think Docker doesn't really work with nftables either, so that one isn't on Podman. It just so happened we made that switch at the same time. Regardless, there were other problems. I'll check to see if I can find any records of the problems later.

Re: Transitioning from Docker to Podman

#204

Post by torvald »

torvald wrote: post #202
IceWreck wrote: post #200

For anyone not using Podman just because lack of docker compose like functionality, there are multiple alternatives. * Podman's official stance is to use Kubernetes YAML. The provide tools to generate this as well as convert docker-compose to kubeyaml * podman-compose is not official, but it works well. you have to note that its not 100% compatible with dc but a lot of dc files run out of the box without modification…

I pray for a Hashicorp Nomad driver as well!

Hi, it exists https://www.nomadproject.io/docs/drivers/podman>! This has gone right passed me.

Re: Transitioning from Docker to Podman

#206

Post by raesene9 »

zelly wrote: post #126

It's compatible with cgroups v2 unlike the standard Docker. If you're using Fedora, you have to add a kernel parameter to Grub to use cgroups v1 instead. RedHat seems to be pushing a standard ecosystem for Linux: systemd, Wayland, SELinux, GNOME, and now maybe podman. I've been on Linux for a while; it's a welcome change from all the fragmentation I'm used to. Whereas others try to work around the kernel and implemen…

FWIW, Docker support for cgroups v2 is coming in 20.10 AFAIK

Re: Transitioning from Docker to Podman

#207

Post by maccard »

core-questions wrote: post #40
zomglings wrote: post #31

Earlier quoted context omitted.

Why do you say that docker-in-docker buys him nothing? It's not obvious at all and you go into no detail whatsoever to back up your opinion. In my experience, that is not true at all. Docker-in-docker allows me to deliver smaller images that can fit into a CI flow as language plugins instead of shipping a beastly 5G docker image with every possible language runtime I need to support for my CI tool.

> beastly 5G docker image my beastly 12GB image that even includes Matlab wants a word with you

Our images are 35GB, and I've spent much of the last two weeks breaking up files so we don't hit the 8GB per file limit, and my next week will be trying to avoid hitting the per-layer limit.

Re: Transitioning from Docker to Podman

#208

Post by ahartmetz »

MrBuddyCasino wrote: post #196
mseidl wrote: post #182

Earlier quoted context omitted.

We have our LTSS -> Long term support at SUSE. Just in case you're a big government that wants to throw us lots of money.

Off-topic, but what’s you experience working at Suse? I know a former employee, and what he told me sounded hellish.

I know two people who work or recently used to work at Suse and they liked it quite a bit.

Re: Transitioning from Docker to Podman

#210

Post by colechristensen »

aruggirello wrote: post #188
dariusj18 wrote: post #152

Earlier quoted context omitted.

I think governments prefer redhat because they are consistent and they accept gobs of cash to promise security patches to software that are past their support window.

I don't know about the gobbles of cash, but I'm pretty sure Canonical supports Ubuntu releases way past EOL for paying customers - they call it the ESM (Extended Security Maintenance), which 'provides important security fixes for the kernel and the most essential user space packages in Ubuntu'.

It tends to also be in the opposite direction, big expensive enterprise software is supported on redhat forever and ever. And the issue isn’t just security updates, but full software and hardware support for the same stack for many years.

Lots of people don’t want to recreate their stack every few years for the latest cool thing.

Post reply on HN