Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Associated nydus image can't be recognized #19452

Closed
imeoer opened this issue Oct 17, 2023 · 0 comments · Fixed by #19453
Closed

Associated nydus image can't be recognized #19452

imeoer opened this issue Oct 17, 2023 · 0 comments · Fixed by #19453

Comments

@imeoer
Copy link
Contributor

imeoer commented Oct 17, 2023

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:

Expected: nydus images are compatible with both docker scheme v2 and OCI image spec v1 types of config media type.
Actual: the associated nydus image can't be recognized as a nydus accessor if it using the docker scheme v2 config type.

Steps to reproduce the problem:

  1. Convert an OCI v1 image to a nydus image with OCI reference type:
nydusify convert \
  --source 192.168.64.7/library/busybox \
  --target 192.168.64.7/library/busybox:latest-nydus \
  --oci \
  --with-referrer
  1. The converted nydus image is not associated with the original OCI v1 image in the harbor portal UI.

Versions:

  • harbor version: v2.9
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants