Kohei Tokunaga

- CRI-O v1.25.1 https://github.com/cri-o/cri-o/releases/tag/v1.25.1 - containers/common v0.49.2 https://github.com/containers/common/releases/tag/v0.49.2 ~~I'll release v0.12.1 after this.~~ Will add a CI for image creation. (#940)

#715 This commit adds a CI to push Kind node image to `ghcr.io/stargz-containers/${VERSION}-kind` namespace on each release. - Example: [`ghcr.io/ktock/stargz-snapshotter:0.0.0-kind`](https://github.com/ktock/stargz-snapshotter/pkgs/container/stargz-snapshotter/45373809?tag=0.0.0-kind) - https://github.com/ktock/stargz-snapshotter/actions/runs/3234126466/jobs/5296849182 ```console $ cat /tmp/kindconfig.yaml kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4...

monitor: Enable to run build and invoke in background

7

#1104 This commit enables to launch builds in a background process and adds some related commands. Please give me feedbacks on the design of the detaching and the CLI. This...

https://github.com/bytecodealliance/wasmtime/releases/tag/v14.0.0

Enable remote snapshotter to receive creds from containerd CRI plugin

16

https://github.com/containerd/stargz-snapshotter/issues/270 https://github.com/kubernetes-sigs/kind/pull/2076#pullrequestreview-591224262 ## Issue Though CRI plugin uses creds passed from kubelet (e.g. `kubernetes.io/dockerconfigjson` secrets) to pull images from the private registries, these creds aren't accessible from (remote) snapshotters. So...

Transfer Service: support remote snapshotters

2

### What is the problem you're trying to solve With the transfer service, remote snapshotters relying on [snapshot annotations](https://github.com/containerd/containerd/blob/e814b03c7488bd8982c97ecd050b33cecaf34037/pkg/snapshotters/annotations.go#L28-L45) (e.g. stargz snapshotter) can't perform lazy pulling because the transfer service...

Transfer: Registry: Enable to use registry configuration diretory

3

Currently transfer service isn't aware of configurations of hosts directory and ctr's `--hosts-dir` doesn't work. This commit fixes this issue by using `config.ConfigureHosts` instead of `docker.ConfigureDefaultRegistries`. This commit also fixes...

- https://github.com/containerd/stargz-snapshotter/pull/1603 - https://github.com/containerd/stargz-snapshotter/pull/1602 - https://github.com/containerd/stargz-snapshotter/pull/1601

- https://github.com/containerd/stargz-snapshotter/pull/1587 - https://github.com/containerd/stargz-snapshotter/pull/1588 - https://github.com/containerd/stargz-snapshotter/pull/1589 - https://github.com/containerd/stargz-snapshotter/pull/1590 - https://github.com/containerd/stargz-snapshotter/pull/1591 - https://github.com/containerd/stargz-snapshotter/pull/1593 - https://github.com/containerd/stargz-snapshotter/pull/1597

store: Avoid access to Forgotten() before configured

1

Fixes #1594 Our `Lookup()` implementation returns a newly created `*fusefs.Inode` to go-fuse. Then that `*fusefs.Inode` is configured and managed by go-fuse lib. Though [`*fusefs.Inode.Forgotten()`](https://github.com/hanwen/go-fuse/blob/e9e7c22af17af4611b5783a16458647088cc8dec/fs/inode.go#L258) allows status check of that object,...