Kohei Tokunaga

You can change the service name by your own ``` sudo mv /etc/systemd/system/stargz-snapshotter.service /etc/systemd/system/containerd-stargz-grpc.service ```

> CRI-based authentication You need to do the following as well https://github.com/containerd/stargz-snapshotter/blob/v0.11.4/docs/overview.md#cri-based-authentication > You must specify --image-service-endpoint=unix:///run/containerd-stargz-grpc/containerd-stargz-grpc.sock option to kubelet. About https://github.com/containerd/stargz-snapshotter/issues/742#issuecomment-1102185315 , the following look like non-estargz images. >...

@yueyuep Is this still an issue?

Feel free to reopen this with additional info if it's still an issue.

@chenk008 > How about using Kubernetes daemonset to run stargz service? This is very interesting and I was thinking of something similar. There is a bootstrapping issue for achieving this....

Of course, please feel free to open up issues/PRs for achieving that.

> We can mount host dir /run into Stargz Snapshotter container. I guess at least `/var/lib/containerd-stargz-grpc` (where stargz snapshotter stores snapshots) needs to be visible from containerd. > If stargz...

> can you share the address of this topic? We can discuss there. @xujihui1985 Maybe this is related to https://github.com/containerd/containerd/issues/5667

We strip debug information from the binary by default. Does removing `-` and `-w` from the following Makefile solve it? https://github.com/containerd/stargz-snapshotter/blob/7f024d4e3b860a663f050d55e65c4e1910e6a166/Makefile#L24

@sumeetb25 Could you provide the step of how have you created the optimized eStargz image? Did you enable the optimization feature provided by ctr-remote ? https://github.com/containerd/stargz-snapshotter/blob/v0.6.4/docs/ctr-remote.md