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

Can't get registry manifest on earlier docker clients? #2400

Closed
aza547 opened this issue Jul 12, 2024 · 2 comments
Closed

Can't get registry manifest on earlier docker clients? #2400

aza547 opened this issue Jul 12, 2024 · 2 comments

Comments

@aza547
Copy link

aza547 commented Jul 12, 2024

I raised an issue distribution/distribution#4400 and was redirected here.

Description

Unable to inspect the manifest for registry on some docker builds. Hoping I'm doing something stupid. But maybe something up with the way this is being uploaded to docker.io?

Reproduce

On one instance of WSL:

$ docker version
Client: Docker Engine - Community
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        baeda1f
 Built:             Tue Oct 25 18:02:21 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          27.0.3
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       662f78c
  Built:            Sat Jun 29 00:02:29 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.18
  GitCommit:        ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc:
  Version:          1.7.18
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
$ docker manifest inspect registry:latest
no such manifest: docker.io/library/registry:latest

On another instance of WSL on the same machine:

$ docker version
Client:
 Version:           24.0.9
 API version:       1.43
 Go version:        go1.21.6
 Git commit:        293681613032e6d1a39cc88115847d3984195c24
 Built:             Thu Apr 25 16:39:04 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          24.0.9
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.21.6
  Git commit:       fca702d
  Built:            Sun Jun  9 18:27:57 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.26
  GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
 runc:
  Version:          1.1.9
  GitCommit:        ccaecfcbc907d70a7aa870a6650887b901b25b82
 docker-init:
  Version:          0.19.0
  GitCommit:

$ docker manifest inspect registry:latest
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
    ... 
<truncated manifest>

Expected behavior

Both versions of docker return the manifest.

registry version

Tried with "latest", "2.8.3", "2". Same results.

Additional Info

No response

@yosifkit
Copy link

I believe this is basically a duplicate of moby/moby#43126, and was fixed by docker/cli#3990; So docker cli v23.0.0 and up has the fix for supporting OCI image types.

docker pull and other commands would be able to use the images just fine since 18.06 moby/moby#37359.

@aza547
Copy link
Author

aza547 commented Jul 13, 2024

Thanks a bunch, it does look the same.

@aza547 aza547 closed this as completed Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants