[Bug 925513] Re: plymouth should not run in container

[Michael Adam]

@Serge,

Could you explain why use of --path can lead to X crashing where lxc-create
without --path is not?

My motivation was: I don't want lxc-create to create the rootfs under /var/lib/lxc.
I need the stuff to be stored elsewhere.
I thought that the --path option in the template was made exactly for this purpose.

Also notice that --path is specified as parameter for the ubuntu template
and not for the lxc-create command:
it is specified after "--" in the command line.

So I think it is really the plymouthd doing something with my framebuffer
(which I assume my X server is also using), somehow eventually killing my
X session. Does that make sense?

I just noticed that I should probably have called lxc-ubuntu with the --trim option.
The description of the option is somewhat misleading:
Looking at the trim() function in the script itself, it in particular disables a couple 
of upstart services: quoting from the script:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls u*.conf); do mv $f $f.orig; done'
    chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls tty[2-9].conf); do mv $f $f.orig; done'
    chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls plymouth*.conf); do mv $f $f.orig; done'
    chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls hwclock*.conf); do mv $f $f.orig; done'
    chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls module*.conf); do mv $f $f.orig; done'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This also explains why another container (lucid) that was created with the --trim
option works without problems. I will re-test the oneiric container with --trim...

Cheers - Michael

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/925513

Title:
  plymouth should not run in container

Status in “lxc” package in Ubuntu:
  Confirmed
Status in “plymouth” package in Ubuntu:
  Incomplete

Bug description:
  Once upstart knows whether it is running in a container, plymouth
  should not run in a container.  As stgraber said, "it writes some
  error messages to /var/log/upstart (when you have logging) and
  sometimes to the console".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions