Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman pull from docker.io - unauthorized #7780

Closed
cybernet opened this issue Sep 25, 2020 · 16 comments
Closed

podman pull from docker.io - unauthorized #7780

cybernet opened this issue Sep 25, 2020 · 16 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@cybernet
Copy link

/kind bug

After a successful login with podman login docker.io

I cannot pull anything because authorization is required ...

Steps to reproduce the issue:

  1. podman login docker.io

  2. podman pull pi-hole/pi-hole

Result

[root@cent0 ~]# podman pull pi-hole/pi-hole
Trying to pull registry.access.redhat.com/pi-hole/pi-hole...
  name unknown: Repo not found
Trying to pull registry.redhat.io/pi-hole/pi-hole...
  unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
Trying to pull docker.io/pi-hole/pi-hole...
  denied: requested access to the resource is denied
Error: error pulling image "pi-hole/pi-hole": unable to pull pi-hole/pi-hole: 3 errors occurred:
	* Error initializing source docker://registry.access.redhat.com/pi-hole/pi-hole:latest: Error reading manifest latest in registry.access.redhat.com/pi-hole/pi-hole: name unknown: Repo not found
	* Error initializing source docker://registry.redhat.io/pi-hole/pi-hole:latest: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
	* Error initializing source docker://pi-hole/pi-hole:latest: Error reading manifest latest in docker.io/pi-hole/pi-hole: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:            1.6.4
RemoteAPI Version:  1
Go Version:         go1.13.4
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.13.4
  podman version: 1.6.4
host:
  BuildahVersion: 1.12.0-dev
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.6-1.module_el8.2.0+305+5e198a41.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.6, commit: a2b11288060ebd7abd20e0b4eb1a834bbf0aec3e'
  Distribution:
    distribution: '"centos"'
    version: "8"
  MemFree: 3318145024
  MemTotal: 3960950784
  OCIRuntime:
    name: runc
    package: runc-1.0.0-65.rc10.module_el8.2.0+305+5e198a41.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree: 4265603072
  SwapTotal: 4265603072
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: cent0
  kernel: 4.18.0-193.19.1.el8_2.x86_64
  os: linux
  rootless: false
  uptime: 10m 27.61s
registries:
  blocked: null
  insecure: null
  search:
  - registry.access.redhat.com
  - registry.redhat.io
  - docker.io
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 0
  GraphDriverName: overlay
  GraphOptions: {}
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 3
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

podman-1.6.4-10.module_el8.2.0+305+5e198a41.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

No

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 25, 2020
@vrothberg
Copy link
Member

Does it work if you pull by fully-qualified name docker.io/pi-hole/pi-hole?

@cybernet
Copy link
Author

cybernet commented Sep 25, 2020

Does it work if you pull by fully-qualified name docker.io/pi-hole/pi-hole?

no, it doesn't.
just out of curiosity I also tried with docker:// - same result

@vrothberg
Copy link
Member

Did you login as root and pulled as root?

@rhatdan
Copy link
Member

rhatdan commented Sep 25, 2020

You must podman login first to get this image.

@rhatdan rhatdan closed this as completed Sep 25, 2020
@vrothberg
Copy link
Member

I'll re-open as the issue states that it's failing despite the login.

@vrothberg vrothberg reopened this Sep 25, 2020
@rhatdan
Copy link
Member

rhatdan commented Sep 25, 2020

Does it succeed on Docker then, and Not on Podman?

@rhatdan
Copy link
Member

rhatdan commented Sep 25, 2020

Can you try with a newer version of Podman?

@cybernet
Copy link
Author

Can you try with a newer version of Podman?

You must podman login first to get this image.

try reading again 😃

@cybernet
Copy link
Author

Did you login as root and pulled as root?

see output of the command - everything is done as root :)

@cybernet
Copy link
Author

I have also tried with podman 2.1 from Solus distro, same result
Has any of you able to reproduce this ?

@vrothberg
Copy link
Member

Can you try pulling another image? For instance, a private one form your own namespace?

Maybe you don't have permission to access pi-hole?

@rhatdan
Copy link
Member

rhatdan commented Sep 29, 2020

Could you attempt to pull the image with Skopeo and or buildah to see if they act differently?

@QiWang19
Copy link
Contributor

QiWang19 commented Oct 8, 2020

This is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1867495 that has been fixed. So close this.

@QiWang19 QiWang19 closed this as completed Oct 8, 2020
@balthild
Copy link

balthild commented Mar 13, 2021

Original comment

Hello. The bugzilla link shows that the problem is fixed in podman v1.6.4, but I still encountered a similar problem in podman v3.0.1

[root@wsl ~]# podman login docker.io
Authenticating with existing credentials...
Existing credentials are valid. Already logged in to docker.io

[root@wsl ~]# podman pull php-7.3:fpm
Resolving "php-7.3" using unqualified-search registries (/etc/containers/registries.conf)
Trying to pull docker.io/library/php-7.3:fpm...
  denied: requested access to the resource is denied
Error: Error initializing source docker://php-7.3:fpm: Error reading manifest fpm in docker.io/library/php-7.3: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

[root@wsl ~]# podman pull docker.io/php-7.3:fpm
Trying to pull docker.io/library/php-7.3:fpm...
  denied: requested access to the resource is denied
Error: Error initializing source docker://php-7.3:fpm: Error reading manifest fpm in docker.io/library/php-7.3: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

[root@wsl ~]# podman version
Version:      3.0.1
API Version:  3.0.0
Go Version:   go1.16
Git Commit:   c640670e85c4aaaff92741691d6a854a90229d8d
Built:        Sun Feb 21 23:29:46 2021
OS/Arch:      linux/amd64

Edit: It's a typo... The correct image is docker.io/php:7.3-fpm. I'm sorry...

@scheidelerl
Copy link

Original comment
Edit: It's a typo... The correct image is docker.io/php:7.3-fpm. I'm sorry...

I get the image by podman pull docker://uselagoon/php-7.3-fpm

@cybernet
Copy link
Author

cybernet commented Jan 9, 2023

Original comment
Edit: It's a typo... The correct image is docker.io/php:7.3-fpm. I'm sorry...

I get the image by podman pull docker://uselagoon/php-7.3-fpm

👍🏼

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

7 participants