-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
push: always inherit distribution sources from parent #9280
push: always inherit distribution sources from parent #9280
Conversation
Hi @vvoland. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
We either need to overlook the win-2019 test failure, or @vvoland needs to rebase on current |
Propagate parent distribution source labels to each of its children even if they're not missing. This allows to cross-repo mount blobs when the child content has different distribution source label from its parent manifest/index. This could happen when different parts of image were fetched from different sources. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
5a1c72c
to
c51d4f9
Compare
Rebased |
/cherrypick release/1.7 |
@samuelkarp: new pull request created: #9452 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Propagate parent distribution source labels to each of its children even if they're not missing. This allows to cross-repo mount blobs when the child content has different distribution source label from its parent manifest/index. This could happen when different parts of image were fetched from different sources.
This extends the behavior from #9029 to all content (not only the missing content).