-
Notifications
You must be signed in to change notification settings - Fork 114
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
lazy pull from private registry #1107
Comments
We are experiencing the same issue. We have configured stargz-snapshotter with containerd as described in the docs. The supplied pre built images are pulling lazily with no issues (can confirm from logs and also can see the fuse mount), but when pushing the pre built image to our own Docker repository it fails to pull lazily and prints the following error (this happens also when the repository is public, not just private):
We have configured CRI based authentication as described here. containerd config:
stargz config.toml:
stargz process is running with the following flags:
And kubelet is running with the stargz-snapshotter service has been restarted, followed by containerd and finally kubelet. Is there anything wrong with our setup or configuration? We really are out of ideas here and would appreciate your help. Thank you very much |
@Dadavan Looks like the image isn't formatted as eStargz. Could you provide the commands used for creating and pushing the image? |
In the above case I simply pulled one of the pre built images, tagged it and pushed to my own repo:
We did also try building our own images but encountered the same problem, in that case the command we used was:
|
Does using other image tools (e.g.
This should work even with Docker Hub. Which BuildKit version are you using? BuildKit >= v0.10 is needed. |
I tried performing the same steps with |
Hi folks, anything new with this? |
@hagaibarel, I think there were two different issues in this thread, not sure which one you're looking for updates on:
When using the |
Hello !! I'm trying out this Snapshotter (Stargz-Store) service and ended up in a similar situation. Following is the log snippet that has some of the error logs collected from the stargz service
I'm using cri-o as the container manager for my cluster and I also tried the workaround mentioned by @dmosdallas but didn't work. @ktock do you have any leads on this? |
Hi,
I have now a setup with rootless podman and the stargz-store running, which works with the pre-converted-images
The stargz-store creates for that pull the following log messages.
But when I pull my own created Image this will not work properly
After that, I pushed one of the pre-converted-images in my private registry and tried to pull that, but it end with similar messages.
Because of the
401 Unauthorized
Error, I did also switch the accessibility of that specific repository to public, but with the same result.Thanks for any help on this!
The text was updated successfully, but these errors were encountered: