[Bug 925513] [NEW] plymouth should not run in container

Serge Hallyn 925513 at bugs.launchpad.net
Thu Feb 2 15:01:21 UTC 2012


Public bug reported:

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

** Affects: lxc (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: plymouth (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Changed in: lxc (Ubuntu)
       Status: New => Confirmed

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Medium

** Also affects: plymouth (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: plymouth (Ubuntu)
       Status: New => Confirmed

** Changed in: plymouth (Ubuntu)
   Importance: Undecided => Medium

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

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




More information about the foundations-bugs mailing list