From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Update podman, buildah, crun
Date: Thu, 08 Apr 2021 04:15:09 +0200 [thread overview]
Message-ID: <20210408021509.k6aMyTl5de3n4frdM67p7AlV-jus99miItaX6JWXBbk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29967@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
There's a closed pull request on the void-packages repository
Update podman, buildah, crun
https://github.com/void-linux/void-packages/pull/29967
Description:
In addition to the update, I've moved `podman` and `buildah` from `runc` to `crun`. `crun` is produced by the same organization and advertises better speed and lower memory footprint. More importantly, with `void-runit` supporting cgroupsv2-only `CGROUP_MODE=unified` mounts (see `/etc/rc.conf`), `podman` does not work out of the box with `runc` but works just fine with `crun`. In fact, when `crun` is installed alongside `runc`, `buildah` prefers `crun`.
I don't know whether `runc` can be made to work with the unified cgroupsv2 mount or whether there are any potential breakages if `runc` is replaced with `crun`.
@CameronNemo @kartikynwa @lemmi
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
prev parent reply other threads:[~2021-04-08 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 4:43 [PR PATCH] " ahesford
2021-04-03 4:46 ` [PR PATCH] [Updated] " ahesford
2021-04-03 6:51 ` kartikynwa
2021-04-03 12:32 ` lemmi
2021-04-04 18:19 ` CameronNemo
2021-04-07 20:13 ` lemmi
2021-04-08 2:15 ` ahesford
2021-04-08 2:15 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210408021509.k6aMyTl5de3n4frdM67p7AlV-jus99miItaX6JWXBbk@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).