We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have found that since ublue-os/main#28 was implemented I have a problem with a podman build use case.
podman build
When I do a local podman build -t Containerfile foo the build succeeds, and results in an image being created.
podman build -t Containerfile foo
but then... when I do podman build -t Containerfile foo2 the final step fails and the image is not created.
podman build -t Containerfile foo2
The resulting error is like this
[2/2] COMMIT foo2 Error: copying image "4f4d5f3b2f00971d1455bcbe0e5d4c86529bff0fc79f10fe2945d94e37251113": Source image rejected: Running image containers-storage:[overlay@/home/benjamin/.local/share/containers/storage+/run/user/10000/containers]@4f4d5f3b2f00971d1455bcbe0e5d4c86529bff0fc79f10fe2945d94e37251113 is rejected by policy.
I have already found a working solution. There is a transport missing in /etc/containers/policy.json.
By adding containers-storage as another transport with "type": "insecureAcceptAnything" things seem to work as normal again.
containers-storage
"type": "insecureAcceptAnything"
The text was updated successfully, but these errors were encountered:
fix: allow podman to use containers-storage transport locally
ec1e00b
Incidentally fixes typos in dates on spec files which were found during testing. closes #82
fix: allow podman to use containers-storage transport locally (#83)
5836ef9
Incidentally fixes typos in dates on spec files which were found during testing. closes #82 Co-authored-by: Jorge O. Castro <[email protected]>
bsherman
Successfully merging a pull request may close this issue.
I have found that since ublue-os/main#28 was implemented I have a problem with a
podman build
use case.When I do a local
podman build -t Containerfile foo
the build succeeds, and results in an image being created.but then... when I do
podman build -t Containerfile foo2
the final step fails and the image is not created.The resulting error is like this
I have already found a working solution. There is a transport missing in /etc/containers/policy.json.
By adding
containers-storage
as another transport with"type": "insecureAcceptAnything"
things seem to work as normal again.The text was updated successfully, but these errors were encountered: