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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075717
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
Server Team, which is subscribed to lxc in Ubuntu.
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
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
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)
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)
This bug was fixed in the package mountall - 2.45
---
mountall (2.45) unstable; urgency=low
[ Serge Hallyn ]
* mounted-dev.conf: leave consoles alone in a lxc or libvirt container
(LP: #1075717)
-- Steve Langasek steve.langa...@ubuntu.com Wed, 28 Nov 2012
22:07:18 -0800
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu47
---
lxc (0.8.0~rc1-4ubuntu47) raring; urgency=low
* 0230-autodev-makedev-console: Run MAKEDEV(console) before creating
consoles in the container. This is to make up for the fact that
userspace (i.e. mountall)
This bug was fixed in the package mountall - 2.45
---
mountall (2.45) unstable; urgency=low
[ Serge Hallyn ]
* mounted-dev.conf: leave consoles alone in a lxc or libvirt container
(LP: #1075717)
-- Steve Langasek steve.langa...@ubuntu.com Wed, 28 Nov 2012
22:07:18 -0800
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu47
---
lxc (0.8.0~rc1-4ubuntu47) raring; urgency=low
* 0230-autodev-makedev-console: Run MAKEDEV(console) before creating
consoles in the container. This is to make up for the fact that
userspace (i.e. mountall)
As per discussion on #ubuntu-devel, lxc should run MAKEDEV in the
container before setting up its devices.
To do this, teh setup_autodev() function must be split up. We'll first
mount all lxc filesystems (including a fresh /dev), then run MAKEDEV
console in the container, then do the rest of
... except that we can't actually call running-in-container reliably
this early in the boot process; /run is not guaranteed to be mounted (or
seen to be mounted) before /dev.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Have talked through this with hallyn in detail.
- we don't want to change MAKEDEV itself to not clobber existing device nodes,
because in other cases this makes recovery from broken /dev less reliable
- we can't side-step this by making /dev not be a mountpoint within the
container because in
** Branch linked: lp:ubuntu/mountall
--
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/1075717
Title:
mounted-dev must not re-create consoles in a container
To manage notifications about
A lxc tree which is working for me to do MAKEDEV console in the
container is at lp:~serge-hallyn/ubuntu/raring/lxc/lxc-makedev.
--
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/1075717
** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
--
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/1075717
Title:
mounted-dev must not re-create consoles in a
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: mountall (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As per discussion on #ubuntu-devel, lxc should run MAKEDEV in the
container before setting up its devices.
To do this, teh setup_autodev() function must be split up. We'll first
mount all lxc filesystems (including a fresh /dev), then run MAKEDEV
console in the container, then do the rest of
... except that we can't actually call running-in-container reliably
this early in the boot process; /run is not guaranteed to be mounted (or
seen to be mounted) before /dev.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Have talked through this with hallyn in detail.
- we don't want to change MAKEDEV itself to not clobber existing device nodes,
because in other cases this makes recovery from broken /dev less reliable
- we can't side-step this by making /dev not be a mountpoint within the
container because in
** Branch linked: lp:ubuntu/mountall
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075717
Title:
mounted-dev must not re-create consoles in a container
To manage notifications about this bug go
A lxc tree which is working for me to do MAKEDEV console in the
container is at lp:~serge-hallyn/ubuntu/raring/lxc/lxc-makedev.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075717
Title:
** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075717
Title:
mounted-dev must not re-create consoles in a container
To
Marking high priority because without this we cannot use separate /dev
partitions in a container.
** Changed in: mountall (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
26 matches
Mail list logo
