vic icon indicating copy to clipboard operation
vic copied to clipboard

not working with v2-only registry

Open greut opened this issue 6 years ago • 4 comments

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

:rainbow:

Logs

n/a

Troubleshooting attempted

  • [x] Searched [GitHub][issues] for existing issues. (Mention any similar issues under "See also", above.)
  • [x] Searched the [documentation][docs] for relevant troubleshooting guidance.
  • [x] Searched for a relevant [VMware KB article][kb].
  • [x] Read the source code

greut avatar Jun 21 '19 15:06 greut

my bad 1 and 2 means schema version. #8566

greut avatar Jun 24 '19 10:06 greut

is there any action required on this ticket still?

michmike avatar Jul 23 '19 22:07 michmike

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

Cheers,

greut avatar Jul 27 '19 09:07 greut

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.

mariolenz avatar Jan 19 '20 17:01 mariolenz