Introduction to runc

#1

Post by prakashdanish » Sun, Sep 06, 2020, 9:21 AM UTC

Re: Introduction to runc

#2

Post by eatonphil » Tue, Sep 08, 2020, 1:35 PM UTC

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

Re: Introduction to runc

#3

Post by nezirus » Tue, Sep 08, 2020, 1:50 PM UTC

In addition to runc, I'd like to point out an alternative OCI runtime implementation, crun (https://github.com/containers/crun). You can play with both either directly, or through Podman (https://podman.io/)

Useful for cgroups v2 too.

Re: Introduction to runc

#4

Post by Tepix » Tue, Sep 08, 2020, 1:52 PM UTC

eatonphil wrote: post #2

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

I hate when they do that. Here is a bookmarklet that will fix those pages:

    javascript:document.querySelector('meta[name=viewport]').setAttribute('content','width=device-width,initial-scale=1.0,maximum-scale=10.0,user-scalable=1');

The real fix is of course to complain to the page author.

Re: Introduction to runc

#5

Post by eatonphil » Tue, Sep 08, 2020, 1:53 PM UTC

Are there any runc shims that just use processes (I know, containers are just processes) ignoring network/user/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.

The point of this would be to take advantage of the Docker ecosystem for _scheduling_ particularly in developer environments. Specifically I'd like a "docker-compose for processes" 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.

Re: Introduction to runc

#6

Post by eatonphil » Tue, Sep 08, 2020, 1:56 PM UTC

nezirus wrote: post #3

In addition to runc, I'd like to point out an alternative OCI runtime implementation, crun ( https://github.com/containers/crun ). You can play with both either directly, or through Podman ( https://podman.io/ ) Useful for cgroups v2 too.

The really weird thing about this is that latest Fedora (by Red Hat, as is crun) doesn't even support cgroups v2. Or I couldn't figure out how to get it working. I had to disable v2 and go back to v1 and use runc.

Re: Introduction to runc

#7

Post by jpitz » Tue, Sep 08, 2020, 2:04 PM UTC

eatonphil wrote: post #2

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

Checking the desktop site checkbox on Android chrome fixed that for me.

Re: Introduction to runc

#8

Post by [deleted] » Tue, Sep 08, 2020, 2:28 PM UTC

[deleted]

Re: Introduction to runc

#9

Post by fetbaffe » Tue, Sep 08, 2020, 2:34 PM UTC

As a Scandinavian I read this as "Introduction to runk" because c at the end of a word is pronounced as k as long it isn’t an abbreviation. Bit unfortunate.

Please downvote.

Re: Introduction to runc

#10

Post by vishvananda » Tue, Sep 08, 2020, 2:45 PM UTC

nezirus wrote: post #3

In addition to runc, I'd like to point out an alternative OCI runtime implementation, crun ( https://github.com/containers/crun ). You can play with both either directly, or through Podman ( https://podman.io/ ) Useful for cgroups v2 too.

There is also a rust implementation that I wrote in my time at Oracle. Unfortunately they no longer maintain it, but there is a fork with some more recent updates: https://github.com/drahnr/railcar