LXC Container Boot/Shutdown errors

[Buzz]

I'm hoping that some of the experienced LXC users in here can help me out with a couple of errors.

I've used the lxc-gentoo script to produce a container and so far it gets me to a booting container which seems to work, but with the following issues:

1) I get the following message on boot.

Code: Select all

* Remounting root filesystem read-only ...
mount: / is busy                                                          [ !! ]

2) I experience the following on a "shutdown -h now" from within the container:

Code: Select all

umount: devpts busy - remounted read-only
umount: /: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))                      [ !! ]
Give root password for maintenance
(or type Control-D to continue): 
INIT: no more processes left in this runlevel

3) Once I have performed a shutdown -h from within the container, I cannot start the container again as it fails with:

Code: Select all

lxc-start: Permission denied - failed to create pty #0
lxc-start: failed to create the ttys
lxc-start: failed to initialize the container

lxc-stop works, of course, however it's a bit of an abrupt stop as it doesn't shut down nicely, but rather appears to kill the processes. I have searched and found the following which is a stretch for me to understand the gentoo/lxc-gentoo solution:

http://www.mail-archive.com/lxc-users@l ... 00867.html

Any help you can provide would be appreciated

Cheers,

Buzz

[Buzz]

There has been limited progress on the /dev/pts issue as follows:

A user Guido Jaekel (sp?) on the lxc-users mailing list has offered the following (and a larger description of what is going on) which I verify to work:

After applying an

host # mount -o remount,rw /dev/pts

the container will be able to startup again.

In addition, running

host # /sbin/init 1

will not remount file systems, but will allow services to be stopped.

It seems there must be a better way in the shutdown scripts to exclude specific file systems from being remounted in read only mode.

Cheers

[Buzz]

I have an additional update:

Besides /dev/pts, there were additional file systems that were being remounted as read-only. This got me to grep for the remount text in /etc and it led me to /etc/init.d/halt.sh

Code: Select all

 
  mobus etc # grep -R "Remounting remaining filesystems" *
  init.d/halt.sh:ebegin "Remounting remaining filesystems readonly"

I then changed the following lines in /etc/init.d/halt.sh

Code: Select all

ebegin "Remounting remaining filesystems readonly"
mount_worked=0
if ! mount_readonly ; then
       if ! mount_readonly ; then
               # If these things really don't want to remount ro, then
               # let's try to force them to unmount
               if ! mount_readonly u ; then
                       mount_worked=1
               fi
       fi
fi

To the following:

Code: Select all

ebegin "Skipping readonly filesystem remounting"
mount_worked=0

#ebegin "Remounting remaining filesystems readonly"
#mount_worked=0
#if ! mount_readonly ; then
#       if ! mount_readonly ; then
#               # If these things really don't want to remount ro, then
#               # let's try to force them to unmount
#               if ! mount_readonly u ; then
#                       mount_worked=1
#               fi
#       fi
#fi

This appears to have solved my read-only file system issues after shutdown within the containers.

Cheers,

Buzz

[dol-sen]

If you still have problems I suggest getting in touch with flameyes or ferringb. They don't frequent the forums much. Both of them are using containers and may be your best bet at getting some good answers. Use their nick at gentoo dot org.