Hi,
I am trying to run concourse CI (CI that run build process into
docker/runc/whatever containers) on systemd-nspawn. I will try to explain
what i do:

1.- First I make a .raw file that install/setup app (with mkosi).
2.- Run concourse container with "systemd-nspawn -bi concourse.raw
--capability=all". App works but fails when starting docker container:

runc create: exit status 1: container_linux.go:264: starting container
process caused "process_linux.go:261: applying cgroup configuration for
process caused \"mkdir
/sys/fs/cgroup/cpuset/8638cb95-bbbc-4719-4509-5a1789fb100a: read-only file
system\""

3.- Run binding cgroups filesystem rw with: "systemd-nspawn -bi
concourse.raw --capability=all --bind=/sys/fs/cgroup". Failing again with:

runc create: exit status 1: container_linux.go:264: starting container
process caused "process_linux.go:339: container init caused
\"rootfs_linux.go:69: creating device nodes caused \\"no such file or
directory\\"\""

Do you have any hint about how can I solve this problem? Thanks in advance.


My system setup, both host and container:
$ cat /etc/issue
Ubuntu 17.10 \n \l

$ systemctl --version
systemd 234 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD -IDN2 +IDN default-hierarchy=hybrid
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to