Thanks Fajar,

it turned out to be simpler: the guest OS was simply missing e2fsprogs, thus sysvinit couldn't switch from runlevel "S" into 2 because of a blocking warning message about failed disk check, indicating the culprit was a /etc/rcS.d/ script. That's what got me believe the container was preset to start in "S". I wasn't aware that "S" scripts are executed even when starting in 2. After installing e2fsprogs, the guest successfully switches to 2.

-- Davide
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users

Reply via email to