Podman 4.4

[wooptoo]

Did they sort out rootless networking? I've tried podman twice but simply cannot get networking to work properly when using a docker-compose file.

[limaho]

I haven’t had issues with rootless networking but I run pretty simple apps. I gave up on podman-compose though and run individual commands to create podman objects. Once rootless containers are in the same pod you can access other containers in the same pod over localhost

[aaravchen]

Since docker-compose is designed to exclusively work with rootful containers (basically the only thing docker supports), it's not a surprise you're having problems trying to run it rootless.

Podman added an optional rootful daemon a few releases ago that you can run in place of/next to the docker daemon that (theoretically) supports all the same docker network functionality specifcally so docker and docker compose commands can be run unchanged on podman.

[galleywest200]

I too have issues with this, but mainly trying to run protected ports (port 53 for DNS with PiHole) as rootless Podman -- it just did not work. Went back to docker and have not had an issue since.

[seized]

Podman 4.0 brought a new network stack for rootless called Netavark. Works nicely for me.

[2OEH8eoCRo0]

What was wrong with it?

[Wronnay]

I hope more open source projects support it.

Most repos I check out still have only docker specific commands…

Even though most things are similar, the differences in e.g networking (for example host.docker.internal vs host.containers.internal) create lots of Issues for me

[candiddevmike]

You may be able to symlink podman to /usr/bin/docker and things should "Just Work"

[AtlasBarfed]

Ok, I really want to use podman, but the last time I built an image and tried to run it, I ran into a brick wall.

I think I used something called buildah to package something, and it had some parameter for a name, but then trying to run it using podman, podman didn't seem to have any way to reference the container image that I THINK buildah created. I think there was also something called spokeo but I don't recall what it did, or it did not help this workflow.

The tutorials all seemed to assume pulling images from the internet.

Anyone have a good podman tutorial that really goes from install podman -> make container -> run container on a Linux box?

[sagarm]

This works for me on Ubuntu 22.10:

  $ sudo apt install podman buildah
  $ mkdir empty && cd empty
  $ cat > Containerfile <<EOF
  FROM alpine:3.14
  RUN echo 'echo hello podman!' > /root/hello.sh
  ENTRYPOINT ["/bin/sh", "/root/hello.sh"]
  EOF
  $ buildah build -f Containerfile -t hello-podman .
  $ podman run -it --rm  localhost/hello-podman:latest
  hello podman!

edit: stryan has more minimalist instructions above.

[stryan]

Were you building from a Dockerfile or Containerfile? If so, you don't need to use buildah you can just use podman build, same as you would docker. So to build an image from a Dockerfile/Containerfile in the current directory just run

podman build -t what_the_image_to_be_tagged .

Then to reference the container by name when you run it, you gotta specify that at runtime:

podman run --name foo the_image_you_just_tagged

[hitori]

There are no builds for Ubuntu 22.04 LTS on arm64, anyone can tell me how to run it on there?

The version in official Ubuntu apt repo is still 3.x ..

[edpenz]

Best solution I've found is installing the v4.3 .debs from Debian bookworm. Only caveat is you need to do some of the dependencies manually as well.

[WirelessGigabit]

How do we encourage other repos like Ubuntu to update to this version? I'd love to have some Ubuntu like distro that has faster / rolling updates for WSL and some VMs. Even the next version of Ubuntu is still stuck on version 3.4...

[antod]

It's in Ubuntu's Universe repository. That means it's usually just the upstream Debian package or one maintained by the community rather than Ubuntu itself.

Ubuntu's podman 3.4 was pulled from Debian Unstable at some point (Debian Stable is still on 3.0?). It looks like Debian Testing has 4.3, so they're probably waiting to just use that from Debian Stable in Ubuntu Lunar rather than the community maintaining their own version.

https://code.launchpad.net/ubuntu/+source/libpod

[yrro]

It's in universe, so I guess wait for the newer package to be pulled from Debian (unstable currently has 4.3.4)?

Or maybe you can request it via the process outlined at https://wiki.ubuntu.com/SyncRequestProcess?

[OJFord]

A not what you're asking, but answer you're actually looking for response might be don't use Ubuntu, use a 'rolling release' distro such as Arch? (Or coming from Ubuntu perhaps the derivative Manjaro.)

[dima55]

By contributing the change you want to see to Debian. Ubuntu is almost entirely a straight rebuild of Debian.

[2OEH8eoCRo0]

This has been out for weeks. Went to check my version and I'm on 4.4.1 (Fedora).

[sphix0r]

What are the benefits of using podman over docker desktop? I've just got my new M1 macbook and are tempting to try docker desktop alternatives..

[cassianoleal]

I don't know how podman machine compares, but I've found colima [0] to be a much better experience to Docker Desktop on Apple Silicon Macs.

[0] https://github.com/abiosoft/colima

[flemhans]

Nice, but seems sort of as complicated as I remember Systemd itself to be.