podman compose uses different authentication file for registry access

[rujutashinde]

This bug is being opened to transfer an issue opened up on podman-desktop. After looking at the issue it was determined that it looked more like a podman issue.

This is the link for the issue podman-desktop/podman-desktop#5438

Following is the description of the issue

Bug description

1. I log into the registry through the UI
2. I successfully pull an image from that registry using podman pull your.registry.com/project/image:latest
3. I try to run podman compose which would pull the same image.
4. -> Authentication fails

Operating system

macOS 14.2.1 (ARM M3)

Installation Method

Brew (macOS)

Version

1.6.3

Steps to reproduce

Install with

brew install podman-desktop
brew uninstall --ignore-dependencies qemu podman
and then install podman in podman-desktop itself, to not run into the current M3 issue with qemu.

Running podman pull your.registry.com/project/image:latest works.

Running podman compose pull which in the file pulls your.registry.com/project/image:latest doesn't.

Relevant log output

No response

Additional context

Workaround: Create a symlink

ln -s /Users/$USER/.config/containers/auth.json /Users/$USER/.docker/config.json

[lsm5]

@rujutashinde Hello, what's the podman version on your system? Would you be able to test with v5.5.0-rc1 released last week?

[github-actions]

A reviewer has determined we need more information to understand the reported issue. A comment on what is missing should be provided. Be certain you:

• provide an exact reproducer where possible
• verify you have provided all relevant information - minimum is podman info
• answer any follow up questions

If no response to the needs-info is provided in 30 days, this issue may be closed by our stale bot.

For more information on reporting issues on this repository, consult our issue guide.

[ninja-quokka]

Hi @rujutashinde, looking at the workaround[1] reported by the user it seems they may have docker-compose installed.

podman compose is a thin wrapper around podman-compose and docker-compose with the latter taking precedence.

More details can be found here, I would either remove docker-compose or set the PODMAN_COMPOSE_PROVIDER environment variable mentioned in the podman-compose docs to verify the issue is with podman-compose.

[1] ln -s /Users/$USER/.config/containers/auth.json /Users/$USER/.docker/config.json