Jan Pazdziora

Note that we use `latest` channel here to get Kubernetes 1.33, so that we don't have to explicitly enable the `UserNamespacesSupport` feature gate.

I observe the same behaviour with `docker.io/octoprint/octoprint:bleeding` of 2025-03-11T14:38:55.082Z as well.

This does not seem to address the issue as observed. Even if I make the `/etc/services.d` writable ``` $ podman run --rm -p 8080:80 --name octoprint --read-only -e S6_READ_ONLY_ROOT=1 --tmpfs...

Last time we discussed this was in https://github.com/freeipa/freeipa-container/issues/321 and there we concluded that `--ip-address` (which you use) should be working. Albeit that was on a master, not replica. But with...

Were you able to make some progress with this? BTW, in https://github.com/freeipa/freeipa-container/pull/640 I'm proposing a way to disable the mechanism which puts the container's internal IP address to DNS, to...

We seem to have lost traction here.

You can try but you are likely the first person to try after ages. The problem is -- you typically want the client container to IPA enroll (if it's not...

Note to self: ``` services: db: image: busybox command: sh -c 'date ; echo I am a db. && sleep 30' init-db: image: busybox command: sh -c 'date ; echo...

On the other hand, podman-compose-1.0.6-3.fc39.noarch ignores the directive and starts `app` right after it starts `init-db`.

Ah, so you try to do something similar to what we did for Atomic: https://projectatomic.io/blog/2015/12/fedora-atomic-sssd-container/ / https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/using_containerized_identity_management_services/configuring-the-sssd-container-to-provide-identity-and-authentication-services-on-atomic-host, not run an IPA-enrolled containerized workload. Seeing https://docs.aws.amazon.com/linux/al2023/release-notes/all-packages-AL2023.3.html contains SSSD, that might work...