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 push to Docker Hub does not "finalize"? #3929

Closed
carlpett opened this issue Sep 3, 2019 · 6 comments
Closed

Podman push to Docker Hub does not "finalize"? #3929

carlpett opened this issue Sep 3, 2019 · 6 comments
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

@carlpett
Copy link

carlpett commented Sep 3, 2019

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

Description
Pushing an image to Docker hub does not seem to "finish all the parts". I'm not sure where exactly it misses something, but it seems the final manifest might not be uploaded?
Docker Hub seems a bit confused about it too - the image doesn't show up in their views, but when working with the special latest tag, it is possible to download it anyway. And pushing again shows that it already has the image

Steps to reproduce the issue:

  1. podman build -t myusername/some-new-image:latest
  2. podman push myusername/some-new-image:latest
  3. (On another machine) pull myusername/some-new-image:latest works
  4. podman tag myusername/some-new-image:latest myusername/some-new-image:v1.0.0
  5. podman push myusername/some-new-image:v1.0.0
  6. (On another machine) pull myusername/some-new-image:v1.0.0 does not work
  7. docker push myusername/some-new-image:latest
  8. (On another machine) pull myusername/some-new-image:v1.0.0 works

Describe the results you received:
Unless pushing with the docker client, tagged images aren't indexed properly by Docker Hub (I believe). And, excepting the latest tag which seems to get special treatment there, they thus cannot be downloaded.

Describe the results you expected:
Works as well as the docker client.

Additional information you deem important (e.g. issue happens only occasionally):
I started this by pushing to a brand new repo. But even after pushing new tags with podman after getting stuff working with the docker client seems to show the same issue.

Output of podman version:

Version:            1.5.1
RemoteAPI Version:  1
Go Version:         go1.12.7
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.12.7
  podman version: 1.5.1
host:
  BuildahVersion: 1.10.1
  Conmon:
    package: podman-1.5.1-3.fc30.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.0, commit: d728afa06cd2df86a27f32a4692c7099a56acc97-dirty'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree: 13342265344
  MemTotal: 33598476288
  OCIRuntime:
    package: runc-1.0.0-93.dev.gitb9b6cc6.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8+dev
      commit: e3b4c1108f7d1bf0d09ab612ea09927d9b59b4e3
      spec: 1.0.1-dev
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 8
  eventlogger: journald
  hostname: XXXXX
  kernel: 5.2.9-200.fc30.x86_64
  os: linux
  rootless: true
  uptime: 78h 9m 3.81s (Approximately 3.25 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /home/XXXXX/.config/containers/storage.conf
  ContainerStore:
    number: 49
  GraphDriverName: overlay
  GraphOptions:
  - overlay.mount_program=/bin/fuse-overlayfs
  GraphRoot: /home/XXXXX/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 309
  RunRoot: /tmp/1000
  VolumePath: /home/XXXXX/.local/share/containers/storage/volumes

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

podman-1.5.1-3.fc30.x86_64

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

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

mheon commented Sep 3, 2019

Hm. Are we pushing the image successfully, but not the tags, I wonder?

@mheon
Copy link
Member

mheon commented Sep 3, 2019

@vrothberg You're a lot more familiar with the image side of things than I am - mind taking a look?

@carlpett
Copy link
Author

carlpett commented Sep 3, 2019

There's probably some sort of bug/usability issue with Docker Hub as well, but I couldn't find any way to report it to them... If you have any connections, might make sense to get them to look at it too :)

@vrothberg
Copy link
Member

@carlpett, @mheon, thanks for opening the issue and the ping. I will have a look at this tomorrow morning (about to shut down machines now).

@TomSweeneyRedHat
Copy link
Member

Is this related to: docker/hub-feedback#1871? Which first cropped up in containers/buildah#1826. It looks like Docker hub is having problems with OCI images at the moment and that should be fixed next week. I think this is the same.

@vrothberg
Copy link
Member

Pushing non-latest tags to the Docker Hub works now. Closing the issue. Again thanks for opening the issue 👍

@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 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 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

5 participants