ChromeOS and Fedora43+ based (penguin) Linux development Environnement

Hi there,

I’ve recently found that any Fedora 43+ containers will break with the few of us using a Fedora based “penguin” default containers that allows to use Linux applications within ChromeOS.

This is on both arches: arm64 and amd64.

First issue is that the default remote for searching lxc compatible “images:” is “missing in action” https://images.linuxcontainers.org/ See also the disclaimer: Important notice for LXD users (image server) - News - Linux Containers Forum

Unfortunately, this have the side effect to only provide the ubuntu: remote…

This issue can be easily fixed by using a new remote as:

(from the Termina VM)

lxc remote add mirror https://images.lxd.canonical.com/ –protocol simplestreams

In this case, you can get a (last known) working Fedora 42 image using:

lxc launch mirror:fedora/42 fedora42
lxc rename fedora42 penguin

And follow with the usual setup as:

Note : I have a working systemd-network in my case and also cros-guest-tool is in the default repos, no need for copr).

Now the second issue that is specific with Fedora 43 and later is that the container will not start in some cases. I’m not sure if all Termina VM are using a similar kernel 6.6.53 with only cgroup-v1 enabled on lxc 5.0.x.

This is caused by the systemd upgrade to deprecate and remove support for cgroup-v1.
(See systemctl status on older container to see the cgroup-v1 taint).

While I haven’t found a formal and approved Fedora feature to remove support for cgroup-v1 in the distribution, this was done as part of an upstream systemd change: https://github.com/systemd/systemd/issues/30852

See also an older non-approved change request:

It seems like systemd upstream have provided a temporary workaround to re-enable cgroup-v1 support, but then the SYSTEMD_CGROUP_LEGACY_FORCE=1 environment variable cannot be in effect without the kernel cmdline See also pid1: stop refusing to boot with cgroup v1 · systemd/systemd@d0ab0e5 · GitHub

So the best workaround for now is probably to keep a f42 systemd using versionlock while upgrading to newer userspace…

Other resources on the topic:

1 Like

See also Fedora 43 and Crostini - #2 by sergiomb

I just copied some excerpts from here to make a summary for you.

Maybe we need to create a systemd package with cgroup-v1 support.

1 Like

And much appreciated!