-
Notifications
You must be signed in to change notification settings - Fork 123
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
stargz-snapshotter doesn't work #245
Comments
By the way I had the same problem even with |
@rsmitty Have you tested if the |
@rsmitty is this relevant anymore? |
It doesn't just not work, it seems to break kubelet ImageGC, and then you'll eventually run out of space.
|
This is a bug in stargz-snapshotter (or even containerd). See containerd/stargz-snapshotter#1349 |
I was thinking that I may just cheese it and create that path as part of the extension, however. But that will come after I can get some time to figure out why we can't pull from a private registry :/ |
- Disable stargz-snapshotter: siderolabs/extensions#245 - Disable zfs: siderolabs/extensions#380
- Disable stargz-snapshotter: siderolabs/extensions#245 - Disable zfs: siderolabs/extensions#380
I installed this extension and tried to run a test pod with the
estargz
image:Getting this error:
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "node": executable file not found in $PATH: unknown
I also see these errors in the
ext-stargz-snapshotter
service.The text was updated successfully, but these errors were encountered: