containerd

Description

context: lima-vm/lima#543 (comment)

Some flags are designed to be nonPersistentAlias (i.e --n, --H) to avoid conflict with submodules. We

Feature Request

Especially since adding contexts can be automated, we should add a context remove CLI option, as well.

talosctl context remove XXXX

Ideally, this should allow glob patterns, too: talosctl context remove talos-default-*.

Description

Expected Behaviour

When users list or query functions from the REST API, then the memory limits set on the functions should be returned in the JSON response.

Current Beha

if using one of the GitHub dark themes, it is near impossible to view documentation images such as

https://github.com/firecracker-microvm/firecracker-containerd/blob/main/docs/img/design-overview.png

and

https://github.com/firecracker-microvm/firecracker-containerd/blob/main/docs/img/design-sequence-diagram.png

due to their usage of black text and transparent background.

It would b

We should have docs for running stargz with popular Kubernetes services and distros.

GKE guide by @rochaporto: https://ricardorocha.io/blog/gke-custom-containerd/ https://twitter.com/lukasheinrich_/status/1362445073045192705

runner集成了weakpass等插件，但是不支持weakpass的自定义字典等非通用化参数设置

A personal idea by @hsiangkao, but I agree with the point.

1. Allow ctr/crictl/nerdctl pull directly without nydus snapshotter;
2. Use zstd:chunked/estargz compression algorithm for blob layer;
3. Allow lzay pull for each blob layer with nydus snapshotter;
4. The bootstrap layer (as final layer) is compatible with erofs format (erofs on fscache), and wrap with tar (allow pulling without ny

Currently, ctriface/ doesn't pick up environment variables from the knative manifests. Firecracker-containerd supports it at a the container creation time as a runtime argument to the corresponding API call.

Example:

	container, err := o.client.NewContainer(
		ctx,
		vmID,
		containerd.WithSnapshotter(o.snapshotter),
		containerd.WithNewSnapshot(vmID, *vm.Image),
		containerd.With