If I create a container from the same image but on runc, updating glibc does not lead to such issue(and systemd does not work, obviously).
Any ideas how to get around the issue? @ctalledo @rodnymolina
EDIT:
Extra data from original comment:
Welcome to Arch Linux!
Failed to create /init.scope control group: Operation not permitted
Failed to allocate manager object: Operation not permitted
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...
This issue is a result of debugging of a problem initially described in https://github.com/nestybox/sysbox/issues/269#issuecomment-824755263
It seems that if I take image https://hub.docker.com/r/nestybox/archlinux-systemd it will install - OK But if you ran
pacman -Syu
, it will not run next time andpacman
gonna give out the error:This is just the tip of the iceberg and most or all of the commands will not work since that point(besides
bash
I think).The issue can be minimized to following use-case:
pacman -Sy glibc
and install new versionOriginal glibc package:
New package:
Focal has:
If I create a container from the same image but on runc, updating glibc does not lead to such issue(and
systemd
does not work, obviously).Any ideas how to get around the issue? @ctalledo @rodnymolina
EDIT: Extra data from original comment: