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

fix(2.7): allow skopeo to use an insecure policy #1859

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

lengau
Copy link
Collaborator

@lengau lengau commented Aug 27, 2024

Fixes this error:

 + charmcraft upload-resource gh-ci-charmcraft-charm example-image --image=docker://hello-world@sha256:18a657d0cc1c7d0678a3fbea8b7eb4918bba25968d3e1b0adebfa71caddbc346
Uploading resource from image charm/co44x4qvu12a2ff5a1v04haywbiyhc0uv6erc/example-image @ docker://hello-world@sha256:18a657d0cc1c7d0678a3fbea8b7eb4918bba25968d3e1b0adebfa71caddbc346.
Checking if manifest is already uploaded
Remote image not found, getting its info from local registry.
Image not found locally. Passing path directly to skopeo.
Running Skopeo
:: time="2024-08-26T18:39:59Z" level=fatal msg="Error loading trust policy: open /etc/containers/policy.json: no such file or directory"
Error while running /snap/charmcraft/x1/libexec/charmcraft/skopeo (return code 1)
Full execution log: '/root/.local/state/charmcraft/log/charmcraft-20240826-183956.163959.log'
-----

@lengau lengau marked this pull request as ready for review August 27, 2024 20:12
@lengau lengau requested a review from a team August 27, 2024 20:12
@lengau lengau changed the title fix: allow skopeo to use an insecure policy fix(2.7): allow skopeo to use an insecure policy Aug 27, 2024
@mr-cal mr-cal requested a review from a team August 27, 2024 20:19
@lengau lengau merged commit d78f516 into hotfix/2.7 Aug 28, 2024
18 of 21 checks passed
@lengau lengau deleted the work/2.7-skopeo-insecure branch August 28, 2024 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants