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 @sebtm:lodere.es
I have an issue since the podman 4 (info/unshare: https://pastebin.com/6Yc9yqtN) -> 5 (info/unshare: https://pastebin.com/tK7safLk) upgrade of my rootless-setup on NixOS: When I'm connected to a vpn (via ProtonVPN app / NetworkManager) the interface used by the bridge / listed in unshare is "ipv6leakintrf0" instead of "tun0" (from the vpn) - before (v4) there was always a tap0 showen with podman unshare. It appears from podman info that both versions (same config) use the "networkBackend: netavark" so I would expect it to behave similar. How can I solve this?

I want to run rootless-podman but need to be connected to vpn/the container to use the vpn-connection/dns provided by the vpn when connected like before.

Hey, using docker-compose with podman (directly and with podman compose) results in:

Apr 23 10:48:00 bsPF1201 podman[171278]: 2024-04-23 10:48:00.460508956 +0200 CEST m=+32.372509043 image pull-error  xyz.de:4567/xyz/abc/image:1.0.2 initializing source docker://xyz.de:4567/xyz/abc/image:1.0.2: Get "https://xyz.de:4567/xyz/abc/image/manifests/1.0.2": dial tcp: lookup xyz.de: Temporary failure in name resolution

it appears to not happen with podman-compose (which I can't use so far because of missing features) - trying to limit the parallel actions/increase retry via engine and docker-compose --parallel 6 pull seems to not help either. Someone an idea?

Hey, using docker-compose with podman (directly and with podman compose) results in:

Apr 23 10:48:00 bsPF1201 podman[171278]: 2024-04-23 10:48:00.460508956 +0200 CEST m=+32.372509043 image pull-error  xyz.de:4567/xyz/abc/image:1.0.2 initializing source docker://xyz.de:4567/xyz/abc/image:1.0.2: Get "https://xyz.de:4567/xyz/abc/image/manifests/1.0.2": dial tcp: lookup xyz.de: Temporary failure in name resolution

it appears to not happen with podman-compose (which I can't use so far because of missing features) - trying to limit the parallel actions/increase retry-delay via engine-config and docker-compose --parallel 6 pull seems to not help either. Someone an idea?

How can I verify engine-config - it does not appear in podman info but I see the entries in /etc/containers/containers.conf:

[engine]
image_parallel_copies = 3
retry_delay = "4s"

Hey, using docker-compose with podman (directly and with podman compose) results in:

Apr 23 10:48:00 bsPF1201 podman[171278]: 2024-04-23 10:48:00.460508956 +0200 CEST m=+32.372509043 image pull-error  xyz.de:4567/xyz/abc/image:1.0.2 initializing source docker://xyz.de:4567/xyz/abc/image:1.0.2: Get "https://xyz.de:4567/xyz/abc/image/manifests/1.0.2": dial tcp: lookup xyz.de: Temporary failure in name resolution

it appears to not happen with podman-compose (which I can't use so far because of missing features) - trying to limit the parallel actions/increase retry-delay via engine-config and docker-compose --parallel 6 pull seems to not help either. Someone an idea?

How can I verify engine-config? It does not appear in podman info but I see the entries in /etc/containers/containers.conf:

[engine]
image_parallel_copies = 3
retry_delay = "4s"

In reply to @sebtm:lodere.es

Hey, using docker-compose with podman (directly and with podman compose) results in:

Apr 23 10:48:00 bsPF1201 podman[171278]: 2024-04-23 10:48:00.460508956 +0200 CEST m=+32.372509043 image pull-error  xyz.de:4567/xyz/abc/image:1.0.2 initializing source docker://xyz.de:4567/xyz/abc/image:1.0.2: Get "https://xyz.de:4567/xyz/abc/image/manifests/1.0.2": dial tcp: lookup xyz.de: Temporary failure in name resolution

it appears to not happen with podman-compose (which I can't use so far because of missing features) - trying to limit the parallel actions/increase retry-delay via engine-config and docker-compose --parallel 6 pull seems to not help either. Someone an idea?

How can I verify engine-config? It does not appear in podman info but I see the entries in /etc/containers/containers.conf:

[engine]
image_parallel_copies = 3
retry_delay = "4s"