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

[Serge Hallyn]

@Michael  (and @Steve)

So plymouth must do stuff over netlink.  Instead of using --trim, you
can simply add the lines from /etc/lxc/lxc.conf to the config file in
your custom path.  By not having those lines, you are telling lxc not to
create a new network namespace.  That means the container is running
plymouth in the host's network namespace, and talking to the host's
upstart over dbus over unix sockets, for instance.

-- 
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