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

[WIP] store: Make additionalimagestores configurable as layerstore source #20604

Closed
wants to merge 1 commit into from

Conversation

idleroamer
Copy link
Contributor

AdditionalImageStores may alter independent of current RWLayerStore resulting in layers references to the ROImageStore, created during the reuseBlob operations, to break.

Optionally allow ignoring stores in AdditionalImageStores as layer store.

Closes: Closes: containers/storage#1751

Does this PR introduce a user-facing change?


Copy link
Contributor

openshift-ci bot commented Nov 6, 2023

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@openshift-ci openshift-ci bot added the do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None label Nov 6, 2023
Copy link
Contributor

openshift-ci bot commented Nov 6, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: idleroamer
Once this PR has been reviewed and has the lgtm label, please assign edsantiago for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

Cockpit tests failed for commit 76f3bcd. @martinpitt, @jelly, @mvollmer please check.

@umohnani8
Copy link
Member

@idleroamer thank you for the PR! However, you are making changes in code that is vendored into podman and need to be fixed in the original containers/storage repo instead.

Can you please open a PR in https://github.com/containers/storage with your changes - once your changes are merged into containers/storage you will have to update this PR to pull in those new changes. The steps for those would be

go get github.com/containers/storage@[latest-commit]
make vendor

@umohnani8
Copy link
Member

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 6, 2023
@giuseppe
Copy link
Member

giuseppe commented Nov 6, 2023

could you explain the proposed fix? If you don't want an additional store, why would you specify it in the config file?

AdditionalImageStores may alter independent of current RWLayerStore
resulting in layers references to the ROImageStore,
created during the reuseBlob operations, to break.

Optionally allow ignoring stores in AdditionalImageStores
as layer store.

Closes: Closes: #20603
Signed-off-by: Mostafa Emami <mustafaemami@gmail.com>
Signed-off-by: 😎Mostafa Emami <mustafaemami@gmail.com>
@rhatdan rhatdan changed the title store: Make additionalimagestores configurable as layerstore source [WIP] store: Make additionalimagestores configurable as layerstore source Nov 6, 2023
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 6, 2023
Copy link

Cockpit tests failed for commit 2e14a94. @martinpitt, @jelly, @mvollmer please check.

continue
}
store = strings.Split(store, "|")[0]
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can’t see how this would work; layers in these stores would be effectively invisible, but images in those stores would be visible as usual.

The immediate effect is that all images from a no-reuse store are visible but have unresolvable layers = look broken to all existing tooling.

Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this would be a much larger work than this.

@@ -344,7 +344,7 @@ Deleted: $pauseID"
driver="overlay"

[storage.options]
additionalimagestores = [ "$imstore/root" ]
additionalimagestores = [ "$imstore/root|NO_REUSE" ]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can invent an infinite number of new options. Please don’t add ambiguous in-line syntaxes unless there is really no other alternative.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, this is just merely a compact version to collect feedback. There should be more agreeable manners to achieve it.

@idleroamer
Copy link
Contributor Author

could you explain the proposed fix? If you don't want an additional store, why would you specify it in the config file?

@giuseppe thanks for the review, I suppose @mtrmac summarize it very well containers/storage#1751 (comment)

@idleroamer
Copy link
Contributor Author

@idleroamer thank you for the PR! However, you are making changes in code that is vendored into podman and need to be fixed in the original containers/storage repo instead.

Can you please open a PR in https://github.com/containers/storage with your changes - once your changes are merged into containers/storage you will have to update this PR to pull in those new changes. The steps for those would be

go get github.com/containers/storage@[latest-commit]
make vendor

thanks, opened containers/storage#1752

@idleroamer idleroamer closed this Nov 6, 2023
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Feb 5, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Usage of AdditionalImageStores as layerstore can break
4 participants