Description

runsc install is able to edit /etc/docker/daemon.json to enable Docker to replace runc with runsc.
Would be great if podman supports this feature.

Is this feature related to a specific bug?

No. By the way, does gVisor depend on Docker just for the reason that Docker uses runsc as its runtime?

Do you have a specific solution in mind?

To replace the runtim

Environment:

• Jib version: 2.5.0
• Build tool: Gradle 6.5.1 (Kotl

On Debian 10, rootless runc (rc92) with --systemd-cgroup fails with a cryptic error when DBUS_SESSION_BUS_ADDRESS is not present in the result of systemctl --user --no-pager show-environment:

https://github.com/opencontainers/runc/blob/2b31437caa905b7b944a891aee613e7dd0a1f898/libcontainer/cgroups/systemd/user.go#L105

This error happens mostly when [dbus-user-session](https://packages

Description
While setting up Cilium 1.8 according to their official documentation on a fresh Kubernetes 1.18 dual-stack cluster with cri-o 1.18.2, I've noticed that the provided connectivity test pods by Cilium 1.8 kept failing their liveness/readiness probes and ended up cra

make tidy currently runs directly on your host relying on the tools and their respective versions. While there is make tidy-in-docker, it is not documented. Let's either replace make tidy in the documentation with make-tidy-docker or change the functionality of make tidy to be containerized.

Per opencontainers/image-spec#803 using zstd compression seems to be on peoples minds.

After reading about it, it seems it's been designed with parallelism in mind, among just being faster on a single core as well. I think it would definitely speed up some of our use cases, at least.

To repro the issue use an image that is not fully qualified as seen below.

 1 ❯ oras push test:test .
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
github.com/deislabs/oras/vendor/github.com/containerd/containerd/reference.Spec.Hostname(0xc000022bb0, 0x9, 0x0, 0x0, 0x147b544, 0xc0001db788)
...