Live data from Hacker News

Introduction to runc

danishpraka.sh

21–30 of 32 posts

Re: Introduction to runc

#21

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.

Why would anyone want to restrict the reader in this way?

Re: Introduction to runc

#22
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.

Did you modified your bootloader with following parameter: systemd.unified_cgroup_hierarchy=1

In runtime, you should see the following:

mount | grep cgroup cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)

btw, I use Arch (yeah I know, the standard adage)

Re: Introduction to runc

#24
post #4

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.

[deleted]

Re: Introduction to runc

#25
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.

Pretty sure runc supports cgroups2 these days.

Not sure why I would want a lot of new C on my machine, unless I was pressed for storage or RAM. Which I am not. runc is like 5MB, which is pretty small for a Go binary.

Re: Introduction to runc

#26
wget directly to /usr/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 /sbin is now a symlink to /usr/sbin on bullseye. Even worse, /lib/modules is a symlink to /usr/lib/modules. Try $ find /lib -name \mlx5\ and learn how find treats symlinks.

Re: Introduction to runc

#27
post #17
post #4

Earlier quoted context omitted.

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.

Reader mode on Firefox does a great job too!

Reader mode in Safari on iOS works great as well, but the zoom level doesn't seem to be fixed, either. It's initially zoomed in but I'm able to zoom out and it will stay.

Re: Introduction to runc

#28
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

Sounds like you are no longer at Oracle. Was this at Oracle Cloud in Seattle? Can you talk about their Rust adoption?

Re: Introduction to runc

#29
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.

Pretty sure runc supports cgroups2 these days. Not sure why I would want a lot of new C on my machine, unless I was pressed for storage or RAM. Which I am not. runc is like 5MB, which is pretty small for a Go binary.

crun is quite a bit faster.

Also `runc` has quite a lot of C in it anyways. The go runtime makes many things very complicated or even impossible.

Re: Introduction to runc

#30

Earlier quoted context omitted.

Isnt that what Foreman and its Procfile handle? https://github.com/ddollar/foreman

Maybe, but I don't want to learn a new config system. Developers are so familiar with docker-compose I just want to use that.

This developer not.
Post reply on HN