docker login compatibility issue

[stratdev3]

Issue Description

There is a docker login registry compatiliby issue.

Steps to reproduce the issue

using the original docker command, everything works fine :

$ docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock docker sh
# echo "mypasswd" | docker login -u mylogin --password-stdin

WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded

but it fails with podman :

$ podman run -it --rm -v $XDG_RUNTIME_DIR/podman/podman.sock:/var/run/docker.sock docker sh
# echo "mypasswd" | docker login -u mylogin --password-stdin
Error response from daemon: login attempt to https://index.docker.io/v1/ failed with status: pinging container registry index.docker.io/v1/: invalid status code from registry 404 (Not Found)

Describe the results you received

unable to login to registry with podman

Describe the results you expected

The login to registry should succeed.

podman info output

$ podman version                                                                                                           125 х │ onedev@sdserver │ 09:12:49
Client:       Podman Engine
Version:      4.3.1
API Version:  4.3.1
Go Version:   go1.19.5
Built:        Tue Jan  1 01:00:00 1980
OS/Arch:      linux/amd64

Podman in a container

Yes

Privileged Or Rootless

Rootless

Upstream Latest Release

No

Additional environment details

Additional environment details

Test with Nixos 22.11 stable release

Additional information

No response

[vrothberg]

Thanks for reaching out, @stratdev3!

The issue seems unrelated to running inside a container but Docker talking to the Podman socket.

DOCKER_HOST=unix:///$XDG_RUNTIME_DIR/podman/podman.sock docker login fails with the same error, so there's something wrong in the compat REST API.

[cristianrgreco]

I see this PR just been merged, thanks! 🚀 Is there any ETA for when this would be released? 🙂

[vrothberg]

@ashley-cui @mheon are there plans for another patch release?

[vrothberg]

I see this PR just been merged, thanks! rocket Is there any ETA for when this would be released? slightly_smiling_face

@cristianrgreco if you need it in RHEL, please open a ticket in the Red Hat Bugzilla.

[stratdev3]

thanks for patch

[mheon]

I was not thinking of another release before 4.5, but we can rethink if we fix something important enough.

…

On Mon, Mar 13, 2023 at 11:44 stratdev3 ***@***.***> wrote: thanks for patch — Reply to this email directly, view it on GitHub <#17571 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCGKQJCLYPW4H3THKE3W346HVANCNFSM6AAAAAAVBR2N3U> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[cristianrgreco]

A patch would be amazing (or a lightning fast release of 4.5 😄), I am trying to integrate podman into our GHA pipelines and am totally blocked as our tests login to private registries. I am currently using 4.4.2 from here: https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Testing

[vrothberg]

Thanks, @cristianrgreco!

@mheon this fix here sounds important. It's somehow surprising it didn't blow up before. It would require some backports in c/common.

[cristianrgreco]

Could this issue also be the reason why IndexServerAddress is empty when calling "/info", or should I raise a new issue?

[vrothberg]

Could this issue also be the reason why IndexServerAddress is empty when calling "/info", or should I raise a new issue?

Please open a new issue. Thank you!