Closed nyodas closed 8 years ago
The success of it depends on the version of the stage1 for the first container (the one that we are in when we run DGR)
ie:
The dgr build will work in.
rkt --stage1-name=coreos.com/rkt/stage1-coreos:1.2.1 run /target/aci-buildbot/image.aci --exec /bin/bash --interactive --net=local --no-overlay
The dgr build won't in.
rkt --stage1-name=coreos.com/rkt/stage1-coreos:1.7.0 run /target/aci-buildbot/image.aci --exec /bin/bash --interactive --net=local --no-overlay
The cgroup filesystems must be mounted in /sys/fs/cgroup/
to start rkt or systemd-nspawn. If you are running rkt inside rkt, /sys/fs/cgroup
needs to be mounted manually because rkt does not do it anymore after https://github.com/coreos/rkt/pull/2681.
There is an open issue about documenting rkt in rkt: https://github.com/coreos/rkt/issues/2158
The message "Failed to determine whether the unified cgroups hierarchy is used" is from systemd-nspawn when it tries to detect how the cgroup filesystems are mounted (unified or not unified). As a workaround, you could export this variable before running rkt:
export UNIFIED_CGROUP_HIERARCHY=no
But it will likely fail a bit later when it tries to use the cgroups.
I don't think it is related to https://github.com/coreos/rkt/issues/1757
/cc @iaguis @lucab
Thx @alban for the information. Took me a bit of time to come back to this. After using your cgroup.sh referenced by the issue of rkt-in-rkt https://github.com/coreos/rkt/issues/2158
It works \o/ . Thanks