-
Notifications
You must be signed in to change notification settings - Fork 297
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
Authentication not working with ostree container unencapsulate
#3015
Comments
We need to support all the proxy options so that custom authentication files can be supported, etc. Closes: ostreedev/ostree#3015
A workaround today is likely |
Thanks for the quick response 🚀 !! The workaround seems to work for unencapsulate
encapsulate
|
For |
The workaround does work with |
We need to support all the proxy options so that custom authentication files can be supported, etc. Closes: ostreedev/ostree#3015
Ideally we'd pass through all of the proxy options here, but doing that sanely really requires being able to do *pushes* through containers-image-proxy-rs, which is a quite nontrivial amount of work. For now, let's pass through `--authfile` which is the main thing people want. Anything else can be worked around by encapsulating to `oci` and then doing a `skopeo copy` from there. cc ostreedev/ostree#3015
And ostreedev/ostree-rs-ext#523 is the other half. |
Ideally we'd pass through all of the proxy options here, but doing that sanely really requires being able to do *pushes* through containers-image-proxy-rs, which is a quite nontrivial amount of work. For now, let's pass through `--authfile` which is the main thing people want. Anything else can be worked around by encapsulating to `oci` and then doing a `skopeo copy` from there. cc ostreedev/ostree#3015
When trying to run
container unencapsulate
in a private repo, I getunauthorized: access to the requested resource is not authorized
When trying with podman, I have no problems pulling the image using
/etc/ostree/auth.json
:I have tried both
/etc/ostree/auth.json
and$HOME/.docker/config.json
and none works. Also running strace I've seen that ostree does open /etc/ostree/auth.jsonIn the end, the only authentication file that is being used is the one set as
global_auth_file
in crio configuration (that in my case happens to be/var/lib/kubelet/config.json
)It be cool if
container unencapsulate
could have an--authfile
flag ascontainer image deploy
hasThe text was updated successfully, but these errors were encountered: