-
Notifications
You must be signed in to change notification settings - Fork 17
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
k3s example: error pulling image #102
Comments
I think the reason why this was failing is because we need to use a |
... and we then need to point k3s's kubelet to use nix-snapshotter image service:
|
Along with #102 (comment), the fix from #107 is required! |
The fix landed so I can now follow-up with a PR with the changes from #102 (comment) 🎉 |
The |
We could patch it with an overlay until we decide to move onto the next stable Nixos release in the future? |
First of all, thanks for the great project! I've always wanted K8S to be declarative all the way down to container images. This is awesome!
I tried running the examples on k3s by commenting out
./kubernetes.nix
in favor of./k3s.nix
in the following file:nix-snapshotter/modules/nixos/vm.nix
Lines 11 to 12 in 6eb21bd
then ran
nix run ".#vm"
to get a VM.Although it successfully boots a VM with k3s, I hit an error when pulling a Nix image like the preloaded one (eg.
kubectl apply -Rf /etc/kubernetes/redis
will result in a pod that fails with a pull image error).Doing the same steps as above but using
./kubernetes.nix
works flawlessly.The text was updated successfully, but these errors were encountered: