Kohei Tokunaga

@dmosdallas > Is there a way to configure the docker buildx plugin to use the --oci-worker-snapshotter=stargz as described in the above docs, or am I totally misunderstanding how this is...

@dmosdallas stargz-snapshotter is embedded to buildktid and it receives creds via docker command over buildkitd API so I believe https://github.com/containerd/stargz-snapshotter/issues/1389#issuecomment-1725949847 should not occur if you use `--oci-worker-snapshotter=stargz`. If it doesn't...

> Could I ask for an explanation for this behavior? I would imagine that one would not want to re-pull images after restarting the daemon. For avoiding leaving empty snapshot...

As of now you can do something like the following for converting the commited image but yes it would be great if docker commit natively support this. ``` cat

@dmosdallas >If this is currently working as expected, is it clear how much effort would be required to teach docker commit to use this snapshotter instead of pulling the full...

Could you provide a reproducer of the issue?

> the container run time is always longer than the create time. Could you also provide your expected performance and your observed one? `create time` is just the latency to...

> docker.io/dadavan/python:3.10-esgz\": 4 error(s) occurred:\n\t* gzip: invalid header\n\t* legacy: failed to get footer gzip reader: gzip: invalid header\n\t* invalid magic number\n\t* gzip: invalid header: failed to resolve target @Dadavan Looks...

@Dadavan > docker Does using other image tools (e.g. [`crane`](https://github.com/google/go-containerregistry)) or other registry (e.g. ghcr.io) solve the issue? > docker buildx build -t bringg/hive:esgz -o type=registry,oci-mediatypes=true,compression=estargz,force-compression=true . This should work...

@allada Maybe you can use prometheus endpoint: https://github.com/containerd/stargz-snapshotter/pull/288