-
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
Write documentation on how to set up /etc/containers/policy.json #530
Comments
Additional note: If user makes the base_path of a distribution the same as the repo name in the remote registry, then no configuration per repo will be needed and it could be just registry name remapping:
|
I would not expand much in our docs on how to setup the policy file since in the specs it is outlined quite well. We can provide some basic example to get user started and for the rest point to the specs. |
I think it makes sense to provide specific examples for what will work with pulp use cases. As a user, I would get lost in terminology between docker, policy and pulp. E.g. A repo(?) name in registry is a base_path in pulp and if you make them the same, it will make your policy maintenance much lighter. My head has already exploded 🤯 |
Signed content is not possible to verify unless there are additional changes to the policy configuration made.
A user who consumes content from the Pulp Registry needs to update the policy (maybe) for each repository separately in order to let
podman
succeed with the pull operation, like so:This has to be properly documented to avoid possible confusion about invalid signatures.
The text was updated successfully, but these errors were encountered: