-
Notifications
You must be signed in to change notification settings - Fork 45
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
As a user I can mount blobs across repositories #494
Milestone
Comments
From: mgoddard (mgoddard) Would love to see this! We have many images which are part of a hierarchy, and have many shared layers. Currently pushing all of these to pulp takes over 3 hours since we have to push all layers for each image. |
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 7, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 8, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 8, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 8, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 9, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 9, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 21, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 21, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Feb 27, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Mar 3, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Mar 7, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Mar 7, 2022
lubosmj
added a commit
to lubosmj/pulp_container
that referenced
this issue
Mar 7, 2022
lubosmj
added a commit
that referenced
this issue
Mar 7, 2022
Hooray! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Author: @ipanova (ipanova@redhat.com)
Redmine Issue: 9241, https://pulp.plan.io/issues/9241
Given that the user, who is currently pushing an image, has READ access to another repository that already contains the blob, he should be able to mount blobs across repositories. The ability, that registry may provide is beneficial to save on network speed.
Cross blob mount works in the following way:
For every repository that container blob X will be asked a token with mount permission. If the user has no READ permission to any of those repos it will fall back and create the blob upload and upload the blob bits.
In these logs the are already existing repos busybox, busybox1, busybox2 that share same blob. Repo
ina/busybox3
is being pushed and it has same blob that is contained in busybox, busybox1 and busybox2.It tries to mount blob against each repo, fails and falls back to the regular blob upload.
https://docs.docker.com/search/?q=Cross%20Repository%20Blob%20Mount
The text was updated successfully, but these errors were encountered: