Getting Podman running on Ubuntu 22.04 LTS

https://gigatexal.blog/pages/getting-podman-on-ubuntu/getting-podman-on-ubuntu.html

by gigatexal • 3 years ago

14 13 3 years ago

gigatexal7• 3 years ago

I'm on a work issued Ubuntu laptop but I very much live (by choice) in the Redhat ecosystem. I wanted to get Podman on my machine but the AD managed user for my laptop was a pain. So having to run it as a user I didn't login as I ran into issues. Anyway, this blog post is more about me having a place to remember the commands to get it working again in the future but also is a love-letter to Podman and Toolbox.

victorstanciu• 3 years ago

The article lists a couple of caveats already, but to me the real hurdle is the lack of a proper alternative to Docker Compose.

debugnik• 3 years ago

Isn't there a separate podman-compose project? Also, I believe you can run much of Docker Compose on top of podman-docker.

gigatexal7• 3 years ago

I’m dumb. When I wrote the article it was late. Docker-Compose really was a game changer.

Yea Podman compose exists. I’ll add a section about docker compose to it in an update.

https://github.com/containers/podman-compose

jck• 3 years ago

You can use the docker compose cli directly since podman exposes the docker api

export "DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock"

aim4min• 3 years ago

One thing I find harder about podman is auto start containers. They should make that easier.

gigatexal7• 3 years ago

I think that’s facilitated by systemd.

Definitely not as easy as a simple flag but this is the proper way to do it. https://linuxhandbook.com/autostart-podman-containers/amp/

viraptor2• 3 years ago

I'm curious what's different in my environment, but the author doesn't mention any issues with apparmor. On my Ubuntu 22.04 AWS instances the default podman/container policies are broken and prevent you from sending signals. That means "podman stop ..." throws permission issues and you can't "kill contained-pid" either.

(Requires either fixing or disabling the policies)

gigatexal7• 3 years ago

Author here. But I’m not sure. My environment is just a vanilla Ubuntu setup with my main login user managed by Centrify AD. It’s a bit odd as the user doesn’t exist in /etc/passwd etc.

What is the error you get? Maybe HN can crowdsource a fix. Or is this a known bug?

viraptor2• 3 years ago

It's this issue; people ran into it since early 2022. I haven't tracked it down in the Ubuntu issues yet, but basically the same thing fails on today's AMIs. https://github.com/containers/podman/issues/13341

The fix is fairly trivial - if you don't care about apparmor you can disable it. If you do, the usual new policy from the complain log is enough.

Getting Podman running on Ubuntu 22.04 LTS

Related Stories