4 ms·
I think your usage example will be easier to understand, if it explains where nix:0 is setup as CRI image-service. Maybe I glanced over it. Awesome project!
by alex_hirner 3y ago
I think your usage example will be easier to understand, if it explains where nix:0 is setup as CRI image-service.
Maybe I glanced over it.
Awesome project!
- hinshun 3y agoHi Alex, I’ve updated the README with a bit more information. 0 is actually an unbindable port, so nix:0 is just an arbitrary string that is unlikely to have conflicts. The Kubelet needs to be configured with —image-service-endpoint to use the nix-snapshotter gRPC socket to handle the “PullImage” RPC. There we can take over resolving the image reference when it’s prefixed with nix:0.