[lxc-users] Ubuntu (maverick) container hangs at init

Fajar A. Nugraha list at fajar.net
Thu May 15 18:31:45 UTC 2014


On Fri, May 16, 2014 at 1:24 AM, Fajar A. Nugraha <list at fajar.net> wrote:


> Works for me. Did you do it like I did?
>
> root at trusty:~# status tty1
> tty1 start/running, process 443
> root at trusty:~# status cron
> cron start/running, process 407
> root at trusty:~# status cron
> root at trusty:~# runlevel
> N 2
>
>
for clarity purpuses: the above commands were executed on the maverick
container. It's just that the hostname of the container is also "trusty"
(since by default the rootfs created in /var/cache/lxc* has hostname the
same as the host)




> - (in the container) create /etc/init/lxc-console.conf
>
> ###
> start on stopped rc RUNLEVEL=[2345] and container CONTAINER=lxc
>

this should be only

start on stopped rc RUNLEVEL=[2345]

container detection only works on newer versions of upstart.





> stop on runlevel [!2345]
>
> respawn
> exec /sbin/getty -8 38400 lxc/console
> ###
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20140516/f3b481d0/attachment-0001.html>


More information about the lxc-users mailing list