podman: Can't push image to docker hub

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Steps to reproduce the issue:

  1. podman pull gcr.io/kubeflow-images-public/katib/v1alpha3/tfevent-metrics-collector

  2. podman tag gcr.io/kubeflow-images-public/katib/v1alpha3/tfevent-metrics-collector yeya24/tfevent-metrics-collector

  3. podman push yeya24/tfevent-metrics-collector

Describe the results you received:

Error copying image to the remote destination: Error trying to reuse blob sha256:8823818c474862932702f8a920abea43b2560ddceb910d145be9ba0eb149a643 at destination: Error checking whether a blob sha256:8823818c474862932702f8a920abea43b2560ddceb910d145be9ba0eb149a643 exists in docker.io/yeya24/tfevent-metrics-collector: errors:
denied: requested access to the resource is denied
error parsing HTTP 401 response body: unexpected end of JSON input: ""

Describe the results you expected:

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

Output of podman version:

$ podman version
Version:       1.0.5
Go Version:    go1.11.5
OS/Arch:       linux/amd64

Output of podman info --debug:

(paste your output here)

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

rpm -q podman
podman-1.0.5-1.gitf604175.module+el8.0.0+4017+bbba319f.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (9 by maintainers)

Most upvoted comments

I faced the same issue with buildah. I had to change my registry to registry-1.docker.io buildah login -u $USERNAME -p $DOCKER registry-1.docker.io

Closing. Please reopen when there’s a reproducer. One thing to check is if there’s proxy between Podman and the registry. Some proxy configurations have shown to cause issue.