PODMAN_COMPOSE_WARNING_LOGS is not respected

[legobeat]

Issue Description

By default, each invocation of podman compose outputs a notice to stderr regardless of configured log-level:

$ podman compose --log-level=error --progress=quiet run --rm --quiet-pull foobar
>>>> Executing external compose provider "/usr/libexec/docker/cli-plugins/docker-compose". Please refer to the documentation for details. <<<<

We would like to silence these without swallowing the stderr from the attached container itself and without editing configuration files on the client or host.

According to podman compose manpage, this line should be possible to disable via the PODMAN_COMPOSE_WARNING_LOGS environment variable but this does not seem effective.

Steps to reproduce the issue

None of these work:

PODMAN_COMPOSE_WARNING_LOGS=false podman compose --log-level=error --progress=quiet run --rm --quiet-pull foobar
PODMAN_COMPOSE_WARNING_LOGS=0     podman compose --log-level=error --progress=quiet run --rm --quiet-pull foobar

(Also tried variations PODMAN_COMPOSE_ENGINE_WARNING_LOGS, COMPOSE_ENGINE_WARNING_LOGS, COMPOSE_WARNING_LOGS)

Neither does attempting to shell around via CONTAINERS_CONF_OVERRIDE:

$ CONTAINERS_CONF_OVERRIDE=<(cat <<EOT
[engine]
compose_warning_logs=false
EOT
) sh -c 'cat ${CONTAINERS_CONF_OVERRIDE}'
[engine]
compose_warning_logs=false

$ CONTAINERS_CONF_OVERRIDE=<(cat <<EOT
[engine]
compose_warning_logs=false
EOT
) podman compose --log-level=error --progress=quiet run --rm --quiet-pull foobar

Forcing it via an actual configuration file does work:

$ cat <<EOT > ./containers-override.conf
[engine]
compose_warning_logs=false
EOT


$ CONTAINERS_CONF_OVERRIDE=$(pwd)/containers-override.conf podman compose --log-level=error --progress=quiet run --rm --quiet-pull foobar

Describe the results you received

Banner is still output regardless of environment variables

Describe the results you expected

Banner is silenced like when setting [engine]\ncompose_warning_logs=false in configuration file.

podman info output

podman version 5.1.2

Linux 6.1 LTS (Fedora 40)

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

Additional environment details

Additional information

Nothing relevant to the issue shows up by changing --log-level=error to --log-level=trace.

[legobeat]

• Addressed in: fix: disable compose_warning_logs if PODMAN_COMPOSE_WARNING_LOGS=false #23442