[Touch-packages] [Bug 1075717] Re: mounted-dev must not re-create consoles in a container
This bug was fixed in the package mountall - 2.36.4ubuntu0.1 --- mountall (2.36.4ubuntu0.1) precise; urgency=medium * mounted-dev.conf: Don't mess with consoles inside containers. (LP: #1075717) -- Stephane Graber stgra...@ubuntu.com Wed, 21 Jan 2015 13:04:17 -0500 ** Changed in: mountall (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1075717 Title: mounted-dev must not re-create consoles in a container Status in lxc package in Ubuntu: Fix Released Status in mountall package in Ubuntu: Fix Released Status in lxc source package in Precise: Invalid Status in mountall source package in Precise: Fix Released Bug description: mounted-dev.conf always does MAKEDEV console. MAKEDEV doesn't just make the devices, it first removes them. When a container starts, it sets up /dev/console and /dev/lxc[1-4] as bind mounts of ptys on the host, for use as lxc consoles. If mounted- dev deletes and recreates those, then none of the lxc consoles work. A simple patch which stops it from breaking lxc consoles is at lp :~serge-hallyn/ubuntu/quantal/mountall/mountall-lxc . However looking back at it, I think it would be ok to do a further check for whether /dev/console exists. If it does not exist, then MAKEDEV console anyway. This isn't necessary, just a thought. == SRU == === Rationale === This bug was fixed in trusty but still affects precise LXC containers that are brought up with /dev mounted as something other than a devtmpfs (which is the case with LXC 1.1). === Test case === - Install LXC 1.1 (from ppa:ubuntu-lxc/daily or in a few days, from vivid) - sudo lxc-create -t download -n precise -- -d ubuntu -r precise -a amd64 - sudo lxc-start -n precise -F That will hang at a blank screen even though the container is functional. - sudo lxc-attach -n precise -- apt-get dist-upgrade -y - sudo lxc-attach -n precise -- reboot And at that point, getty should show up fine in the lxc-start shell. === Regression potential === Not expecting any, the change is straightforward and has been in Ubuntu since raring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1075717] Re: mounted-dev must not re-create consoles in a container
Verified, with -proposed I now get a console in precise container, thanks. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1075717 Title: mounted-dev must not re-create consoles in a container Status in lxc package in Ubuntu: Fix Released Status in mountall package in Ubuntu: Fix Released Status in lxc source package in Precise: Invalid Status in mountall source package in Precise: Fix Committed Bug description: mounted-dev.conf always does MAKEDEV console. MAKEDEV doesn't just make the devices, it first removes them. When a container starts, it sets up /dev/console and /dev/lxc[1-4] as bind mounts of ptys on the host, for use as lxc consoles. If mounted- dev deletes and recreates those, then none of the lxc consoles work. A simple patch which stops it from breaking lxc consoles is at lp :~serge-hallyn/ubuntu/quantal/mountall/mountall-lxc . However looking back at it, I think it would be ok to do a further check for whether /dev/console exists. If it does not exist, then MAKEDEV console anyway. This isn't necessary, just a thought. == SRU == === Rationale === This bug was fixed in trusty but still affects precise LXC containers that are brought up with /dev mounted as something other than a devtmpfs (which is the case with LXC 1.1). === Test case === - Install LXC 1.1 (from ppa:ubuntu-lxc/daily or in a few days, from vivid) - sudo lxc-create -t download -n precise -- -d ubuntu -r precise -a amd64 - sudo lxc-start -n precise -F That will hang at a blank screen even though the container is functional. - sudo lxc-attach -n precise -- apt-get dist-upgrade -y - sudo lxc-attach -n precise -- reboot And at that point, getty should show up fine in the lxc-start shell. === Regression potential === Not expecting any, the change is straightforward and has been in Ubuntu since raring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1075717] Re: mounted-dev must not re-create consoles in a container
Hello Serge, or anyone else affected, Accepted mountall into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mountall/2.36.4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mountall (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1075717 Title: mounted-dev must not re-create consoles in a container Status in lxc package in Ubuntu: Fix Released Status in mountall package in Ubuntu: Fix Released Status in lxc source package in Precise: Invalid Status in mountall source package in Precise: Fix Committed Bug description: mounted-dev.conf always does MAKEDEV console. MAKEDEV doesn't just make the devices, it first removes them. When a container starts, it sets up /dev/console and /dev/lxc[1-4] as bind mounts of ptys on the host, for use as lxc consoles. If mounted- dev deletes and recreates those, then none of the lxc consoles work. A simple patch which stops it from breaking lxc consoles is at lp :~serge-hallyn/ubuntu/quantal/mountall/mountall-lxc . However looking back at it, I think it would be ok to do a further check for whether /dev/console exists. If it does not exist, then MAKEDEV console anyway. This isn't necessary, just a thought. == SRU == === Rationale === This bug was fixed in trusty but still affects precise LXC containers that are brought up with /dev mounted as something other than a devtmpfs (which is the case with LXC 1.1). === Test case === - Install LXC 1.1 (from ppa:ubuntu-lxc/daily or in a few days, from vivid) - sudo lxc-create -t download -n precise -- -d ubuntu -r precise -a amd64 - sudo lxc-start -n precise -F That will hang at a blank screen even though the container is functional. - sudo lxc-attach -n precise -- apt-get dist-upgrade -y - sudo lxc-attach -n precise -- reboot And at that point, getty should show up fine in the lxc-start shell. === Regression potential === Not expecting any, the change is straightforward and has been in Ubuntu since raring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1075717] Re: mounted-dev must not re-create consoles in a container
This needs fixing in precise too. I just ran into that very problem with current upstream LXC and a precise privileged container. I'll upload a straight cherry-pick of the mounted-dev.conf job as we have it nowadays (I confirmed that fixes it here). ** Also affects: lxc (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: mountall (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Precise) Status: New = Invalid ** Changed in: mountall (Ubuntu Precise) Status: New = Triaged ** Changed in: mountall (Ubuntu Precise) Assignee: (unassigned) = Stéphane Graber (stgraber) ** Changed in: mountall (Ubuntu Precise) Importance: Undecided = High ** Description changed: mounted-dev.conf always does MAKEDEV console. MAKEDEV doesn't just make the devices, it first removes them. When a container starts, it sets up /dev/console and /dev/lxc[1-4] as bind mounts of ptys on the host, for use as lxc consoles. If mounted- dev deletes and recreates those, then none of the lxc consoles work. A simple patch which stops it from breaking lxc consoles is at lp :~serge-hallyn/ubuntu/quantal/mountall/mountall-lxc . However looking back at it, I think it would be ok to do a further check for whether /dev/console exists. If it does not exist, then MAKEDEV console anyway. This isn't necessary, just a thought. + + + == SRU == + === Rationale === + This bug was fixed in trusty but still affects precise LXC containers that are brought up with /dev mounted as something other than a devtmpfs (which is the case with LXC 1.1). + + === Test case === + - Install LXC 1.1 (from ppa:ubuntu-lxc/daily or in a few days, from vivid) + - sudo lxc-create -t download -n precise -- -d ubuntu -r precise -a amd64 + - sudo lxc-start -n precise -F + + That will hang at a blank screen even though the container is + functional. + + - sudo lxc-attach -n precise -- apt-get dist-upgrade -y + - sudo lxc-attach -n precise -- reboot + + And at that point, getty should show up fine in the lxc-start shell. + + === Regression potential === + Not expecting any, the change is straightforward and has been in Ubuntu since raring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1075717 Title: mounted-dev must not re-create consoles in a container Status in lxc package in Ubuntu: Fix Released Status in mountall package in Ubuntu: Fix Released Status in lxc source package in Precise: Invalid Status in mountall source package in Precise: Triaged Bug description: mounted-dev.conf always does MAKEDEV console. MAKEDEV doesn't just make the devices, it first removes them. When a container starts, it sets up /dev/console and /dev/lxc[1-4] as bind mounts of ptys on the host, for use as lxc consoles. If mounted- dev deletes and recreates those, then none of the lxc consoles work. A simple patch which stops it from breaking lxc consoles is at lp :~serge-hallyn/ubuntu/quantal/mountall/mountall-lxc . However looking back at it, I think it would be ok to do a further check for whether /dev/console exists. If it does not exist, then MAKEDEV console anyway. This isn't necessary, just a thought. == SRU == === Rationale === This bug was fixed in trusty but still affects precise LXC containers that are brought up with /dev mounted as something other than a devtmpfs (which is the case with LXC 1.1). === Test case === - Install LXC 1.1 (from ppa:ubuntu-lxc/daily or in a few days, from vivid) - sudo lxc-create -t download -n precise -- -d ubuntu -r precise -a amd64 - sudo lxc-start -n precise -F That will hang at a blank screen even though the container is functional. - sudo lxc-attach -n precise -- apt-get dist-upgrade -y - sudo lxc-attach -n precise -- reboot And at that point, getty should show up fine in the lxc-start shell. === Regression potential === Not expecting any, the change is straightforward and has been in Ubuntu since raring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1075717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
