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

not working with v2-only registry #8565

Open
4 tasks done
greut opened this issue Jun 21, 2019 · 4 comments
Open
4 tasks done

not working with v2-only registry #8565

greut opened this issue Jun 21, 2019 · 4 comments
Assignees
Labels
kind/feature New functionality you could include in marketing material

Comments

@greut
Copy link

greut commented Jun 21, 2019

Summary

Using a Nexus registry which doesn't have V1 image, pulling an image fails because it mostly tries to use the v1 (although saying otherwise)

https://github.com/vmware/vic/blob/master/lib/imagec/imagec.go#L621

VIC version

v1.5.2

Steps to reproduce
$ docker run my-nexus-repository/foo/bar
Actual behavior
Error while pulling image manifest: missing signature key.
Expected behavior

🌈

Logs

n/a

Troubleshooting attempted

  • Searched [GitHub][issues] for existing issues. (Mention any similar issues under "See also", above.)
  • Searched the [documentation][docs] for relevant troubleshooting guidance.
  • Searched for a relevant [VMware KB article][kb].
  • Read the source code
@greut greut changed the title not working with v1-only registry not working with v2-only registry Jun 21, 2019
@greut
Copy link
Author

greut commented Jun 24, 2019

my bad 1 and 2 means schema version. #8566

@greut greut closed this as completed Jun 24, 2019
@greut greut reopened this Jun 24, 2019
@renmaosheng renmaosheng added the kind/feature New functionality you could include in marketing material label Jul 2, 2019
@michmike
Copy link

is there any action required on this ticket still?

@greut
Copy link
Author

greut commented Jul 27, 2019

In the meantime, VIC became out of scope for us. That's up to you I'd say.

Cheers,

@mariolenz
Copy link

is there any action required on this ticket still?

I've had a similar problem recently. A "normal" docker was able to pull an image, but vic failed. Naturally, I assumed a vic problem but it turned out that it was a problem with our registry. But only with schema v1, not with schema v2. It's really hard to troubleshoot such an issue when vic doesn't work like a "normal" docker, that is using schema v1 instead of v2.

So I'd say yes, there is some action required on this ticket: Make vic use schema version 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New functionality you could include in marketing material
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants