I'm having trouble sussing out the underlying principle here that
warrants special-casing plymouth in a container. Plymouth is the
standard boot-time I/O multiplexer; any upstart jobs that need to
interact with the user at boot time should be using plymouth. Now for
the most part, this currently consists of mountall and cryptsetup, and I
can understand how it might be that neither of those are relevant in the
context of a container. But what about things like
/etc/init/failsafe.conf? Or a hypothetical apache job that prompts for
an SSL passphrase through plymouth?
So it's not clear to me that disabling plymouth in the container is the
right answer, as opposed to fixing any problems plymouth has when
running. "Writing errors to the console" seems to be part and parcel of
plymouth's responsibilities.
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
