Hello again! Has anybody noticed that the podman-next version from copr doesn't work?
On a vanilla almalinux 9.3 vm, installed podman using https://podman.io/docs/installation#installing-bleeding-edge-versions-of-podman, and even a simple version command gives:

[user@test ~]$ sudo podman version
Error:

The system logs aren't really helpful either, as don't show any errors
The weird thing is that if I run podman version as a regular user it works, only on root user it fails like above

I have two containers running on the same host.
One has traefik in it as a reverse proxy.

I try to access container2 (an app) from container 1(traefik) through the host ip and the respective bound port.
From any other machine this work fine but nut on the same machine from container to container.
Each container is in its own network. When I join them together in one network, it works.
So it seems the communication does not go through the host but directly from container to container.
Is there any way to solve that connectivity issue without joining them into one network?

trying to translate a docker-compose instruction to be more podman compatible, but idk if it works.

here is a line that defined a volume in the original docker-compose file im trynna convert:

• /var/run/docker.sock:/var/run/docker.sock

for podman, it should be rootless, so idk how to translate this line... need a little help 😀️

trying to translate a docker-compose instruction to be more podman compatible, but idk if it works.

here is a line that defined a volume in the original docker-compose file im trynna convert:

volumes:
   - /var/run/docker.sock:/var/run/docker.sock

for podman, it should be rootless, so idk how to translate this line... need a little help 😀️

trying to translate a docker-compose instruction to be more podman compatible, but idk if it works.

here is a line that defined a volume in the original docker-compose file im trynna convert:

volumes:
   - /var/run/docker.sock:/var/run/docker.sock

for podman, it should be rootless, so idk how to translate this line to be rootless... need a little help 😀️

In reply to @baerentoeter:matrix.org
hi guys, im - again - having issues with podman (5.0.0) and selinux: i have a container that starts an sshd on port 22022 using network_mode: host. it works perfeclty fine when selinux is in permissive mode, but i cannot connect to the server when selinux is in enforcing mode. i have followd the steps from https://access.redhat.com/documentation/de-de/red_hat_enterprise_linux/8/html/using_selinux/creating-selinux-policies-for-containers_using-selinux but installing the policy generated by udica fails with "Failed to resolve typeattributeset statement at /etc/selinux/targeted/tmp/modules/400/base_container/cil:6" any ideas?

In reply to @eriksjolund:fedora.im
The sshd problem might be related to this troubleshooting tip https://github.com/containers/podman/blob/main/troubleshooting.md#33-the-sshd-process-fails-to-run-inside-of-the-container