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

Steve Langasek steve.langasek at canonical.com
Fri Feb 17 03:30:25 UTC 2012


> Does it write it straight to /var/log/boot.log, or does it do it through
> syslog(2) or syslog(3)?  If it writes straight to /var/log/boot.log then
> there should be no problem.

Yes, it's straight to the log file.

> /dev/console and /dev/tty{1-4} are bind-mounted pty devices, and are ok
> for it to use.  /dev/fb is not available in the container - I don't see
> /dev/fb0 at all, and the devices cgroup will refuse the container the
> rights to read or write it.  Otherwise it would be a problem as that is 
> not virtualized.

Well, if /dev/fb0 isn't available, plymouth should automatically fall
back to using the console in text-only mode.

> Steve, it sounds to me like we should mark this bug as wontfix.

Ok, done.

** Changed in: plymouth (Ubuntu)
       Status: Incomplete => Won't Fix

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

Title:
  plymouth should not run in container

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



More information about the Ubuntu-server-bugs mailing list