You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are docs related to how to access private registries for the snapshotter with containerd, but I couldn't find any reference on how to achieve the same with the Stargz Store, especially for CRI-O. This issue aims to discuss whether it's possible and whether the project could document that in more details.
The text was updated successfully, but these errors were encountered:
Currently there are docs related to how to access private registries for the snapshotter with containerd, but I couldn't find any reference on how to achieve the same with the Stargz Store, especially for CRI-O. This issue aims to discuss whether it's possible and whether the project could document that in more details.
stargz-store accepts same configuration as stargz-snapshotter(containerd-stargz-grpc) but the default config path of stargz-store is /etc/stargz-store/config.toml. SGTM about improving the documentation for stargz-store (contribution is welcome, of course).
I want to use the snapshotter with the sysbox runtime and currently it doesn't support containerd. Is it possible? Can we document that too?
I'd gladly test any directions you can point me and open a PR for documenting that and if possible add tests.
Currently there are docs related to how to access private registries for the snapshotter with containerd, but I couldn't find any reference on how to achieve the same with the Stargz Store, especially for CRI-O. This issue aims to discuss whether it's possible and whether the project could document that in more details.
The text was updated successfully, but these errors were encountered: