engine.detach_keys is not used correctly with podman compose about podman HOT 4 OPEN

I was trying to debug this and could not reproduce the issue. However, I'm wondering if it has to do with the specific config file that you modified in the first step. Looking at the docs in man containers.conf:

Container engines read the /usr/share/containers/containers.conf, /etc/containers/containers.conf, and /etc/containers/containers.conf.d/.conf files if they exist.
When running in rootless mode, they also read $HOME/.config/containers/containers.conf and
$HOME/.config/containers/containers.conf.d/.conf files.

It mentions that the file you modified in your first step (~/.config/containers/containers.conf) only applies to rootless mode containers. I'm wondering if the podman compose is for some reason not running the container as rootless.

If you take that settings provided and put the config changes in one of the global config files, do you still see this issue?

from podman.

Ah! I think I just had to restart the podman socket daemon... Now after a reboot, I don't reproduce anymore

from podman.

Maybe it is unrelated to this ticket, but I still see a difference in the behavior between podman compose and podman run contexts.

With podman run: there is no <c-p><c-q> shortcut at all

With podman compose run: there is still a <c-p><c-q>, additionnaly to <c-x>x

The following paste show first a <c-p><c-q>, then the <c-x>x

[stacy@yellow-orcess ~/tmp]$ podman compose run --rm foo sh
>>>> Executing external compose provider "/usr/bin/docker-compose". Please refer to the documentation for details. <<<<

/ # ERRO[0002] error waiting for container: context canceled
[stacy@yellow-orcess ~/tmp]$ podman compose run --rm foo sh
>>>> Executing external compose provider "/usr/bin/docker-compose". Please refer to the documentation for details. <<<<

/ # Error: detached from container
                                  pwd

^C[stacy@yellow-orcess ~/tmp]$
``

from podman.

The containers.conf files are onlly read at podman start, in one case you have a podman running locally which reads the containers.conf, In the podman compose case you are talking to the podman service which could have been running before the containers.conf was set?

You can eliminate the podman compose part and just do

podman --remote run ...

And see if the detach keys work properly, after service restart.

from podman.