Introduction to runc

In addition to runc, I&#x27;d like to point out an alternative OCI runtime implementation, crun (<a href="https:&#x2F;&#x2F;github.com&#x2F;containers&#x2F;crun" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;containers&#x2F;crun</a>). You can play with both either directly, or through Podman (<a href="https:&#x2F;&#x2F;podman.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;podman.io&#x2F;</a>)<p>Useful for cgroups v2 too.

Unfortunately on mobile the zoom is fixed (I can&#x27;t zoom out, didn&#x27;t know that was possible) and I can&#x27;t see the left and right edges of the text.

Are there any runc shims that just use processes (I know, containers are just processes) ignoring network&#x2F;user&#x2F;etc namespace isolation and other Linux-specific security features? For example a shim that could run native MacOS processes on MacOS, native FreeBSD binaries on FreeBSD, etc. just by executing the processes directly.<p>The point of this would be to take advantage of the Docker ecosystem for _scheduling_ particularly in developer environments. Specifically I&#x27;d like a &quot;docker-compose for processes&quot; that can run on any system and just handles scheduling multiple processes together but without requiring root access to modify init scripts or systemd services at the system level.

wget directly to &#x2F;usr&#x2F;bin. Am I the only one who cringes upon such a pattern? I am probably too old. I recently almost doubled over when I saw that &#x2F;sbin is now a symlink to &#x2F;usr&#x2F;sbin on bullseye. Even worse, &#x2F;lib&#x2F;modules is a symlink to &#x2F;usr&#x2F;lib&#x2F;modules. Try $ find &#x2F;lib -name \<i>mlx5\</i> and learn how find treats symlinks.