Que ce passait-il lorsque vous démarriez avec 14.04 ? Est-ce que vous
avez essayé de démarrer le CD d'installation de 14.04 ?
Un problème potentiel avec un ordinateur de plus de 7 ans est qu'il ne
supporte pas le PAE et donc ne soit pas capable de démarrer un kernel
recent, un message d'erreur
The solution to this problem will be implemented through live-build
hooks. Sadly the existing set of hooks doesn't quite match what we need,
so this adds a new .chroot_early hook type which runs right after
deboostrap allowing early mangling of the user/group database.
** Package changed:
Fix pushed upstream, thanks!
--
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/1372878
Title:
lxc-download is missing keyserver option mentioned in usage
Status in “lxc”
I've been running LXC 1.0.5 for a while here without any issue, the
upstream test suite and our adt tests have all passed, marking
verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
** Also affects: shadow (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow
Public bug reported:
I've recently ran into a few cases where it'd have been very useful to
be able to grant veth allocations to a group rather than to a user.
This will also be required for running LXC on top of Unity8.
Can we please add a syntax like:
%lxcusers veth lxcbr0 10
Which would
Public bug reported:
We have released LXC 1.0.6 upstream: https://linuxcontainers.org/news
This will be the third upstream bugfix release to hit trusty. The
upstream changes are detailed at the URL above.
The MRE was reviewed by Martin Pitt here:
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Fix uploaded to utopic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
Status in “ifupdown” package in
Public bug reported:
Dear release team,
LXC 1.1~alpha2 was just tagged upstream and we'd like to get that into
Ubuntu 14.10.
The main reasons for this are:
- Isn't broken on the current utopic kernel
- Makes nova-compute-flex work properly
- Fix LXC to work on Ubuntu systems running with
20:59 infinity stgraber: So, yeah, copy and paste to bugs as
necessary, but this is me saying if you can fix things that depend on
the old lxc-start behaviour, please don't revert it, and you're okay for
the alpha2 upload.
So that's a +1 on the plan above with the change that I will not do any
You can read some more about cgmanager at
https://cgmanager.linuxcontainers.org
cgroup-lite's goal was simply to mount the cgroup filesystem in a
consistent manner, cgmanager instead is a daemon which handles all
cgroup actions through a dbus API and allows for proper user delegation
of cgroups
Hey Chris,
This is a parser bug which we need to fix. I believe Serge is looking
into it.
In the mean time, try using append_config_item instead which may work
fine in this case (so long as it's not called multiple times, otherwise
you'll get duplicates).
--
You received this bug notification
Been running it for a few weeks now, works fine.
** 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/1373619
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Can you paste /proc/mounts from your host please?
--
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/1389305
Title:
sudo doesn't work on unprivileged lxc container
Status in
A suggested fix for this would be:
initrd:
- At every boot, do a minimal fsck check for problems, if problem, write fsck
partition to /cache/recovery/ubuntu_command and reboot to recovery
recovery:
- Add support for the fsck stanza, when getting it, run fsck in fix mode, if
possible,
so I think it's some systemd handling which does that. LXC unshares the
mnt namespace which gets it a copy of the host's, then it's doing some
magic (rprivate I believe) to get things working under systemd, then
mounts what it needs, unmounts everything else and pivot_root.
lxc itself has no code
Anything else that's special on that network, e.g. non-standard MTU?
--
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/1402763
Title:
Multicast traffic not propating correctly
: Stéphane Graber (stgraber)
Status: In Progress
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New = Invalid
** Changed in: lxc (Ubuntu Trusty)
Status: New = In Progress
** Changed in: lxc (Ubuntu Trusty
I just checked here and I can install LXC 1.0.5-0ubuntu0.1 and remove it
fine with both apt-get and aptitude.
Looking at the error you're getting, the problem is that you have a
/usr/sbin/policy-rc.d script present on your system. That file is typically
created by debootstrap or other similar
: Medium
Assignee: Stéphane Graber (stgraber)
Status: In Progress
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New = Invalid
** Changed in: lxc (Ubuntu Trusty)
Status: New = In Progress
** Changed
21:46 jibel stgraber, the problem is still there with cgmanager 0.32-4ubuntu1
21:47 stgraber jibel: now that's something I wasn't hoping to hear :)
21:47 stgraber jibel: so I'm guessing the same dbus-send test hangs against
cgmanager/sock and not against cgmanager.lower/sock, right?
21:47
On the next hang, please report the following:
- dbus-send to both bus addresses (confirming the hang)
- ls -lh /proc/$(pidof cgmanager)/fd/
- ls -lh /proc/$(pidof cgproxy)/fd/
- gdb -p $(pidof cgmanager) -ex bt
- gdb -p $(pidof cgproxy) -ex bt
- dmesg
- free
-
Just had a chat with Serge and we've got a theory.
cgmanager sends tasks to cgproxy using ucreds. ucreds contain a pid, uid
and gid, all of which must be valid. If however the pid gets killed and
dies between the time the ucred is generated and the time it's sent over
the socket, it'll be invalid
I agree it'd be nice for the download template to be clever and filter
its output. However the fact that it's very very difficult to know what
your CPU is actually capable of running (especially for arm64, armel,
armhf and powerpc, powerpc64 and ppc64el) and the name for the
architectures changes
13:14 ogra_ stgraber, soo ... that gcmanager fix from hallyn looks reallly
good, the phone seems a lot more stable ... we are wondering what the
implications are if we would use the 0.32 cgmmanager in rtm though ... would
there be any drawbacks with the old lxc version we use ?
13:15 sil2100
Might be worth checking that the same is done for all controllers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413927
Title:
login name=systemd cgroup is not owned by
I have an upstream fix for /proc/sys/net/* which should be writable in
the container (tied to netns), the others still look to me as knobs that
shouldn't be writable in a container and so having the procps return
value be ignored in containers would seem like a reasonable fix to me.
--
You
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
Oh and the same goes for containers that aren't running systemd but are
running logind as logind also expects to be able to create sub-entries
in the name=systemd controller, which with the current cgroup ownership,
it won't be able to do.
--
You received this bug notification because you are a
How are we supposed to run a systemd container on such a system then?
systemd in a container will need to create sub-entries in the
name=systemd controller. If the user doesn't own its cgroup, LXC will
not be able to create the entry for the container and the container will
not be able to write
Hmm, so here the user didn't own the directories which was a good part
of the issue I suspect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413927
Title:
user lxc
Public bug reported:
root@lantea:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# Physical network
May be related to https://github.com/lxc/lxc/issues/406
--
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/1414771
Title:
Can not clone lxc container with lvm backingstore after
We have existing code in procps to ignore EACCES but not for EROFS, I'll
be pushing updates to all series to sort that out.
** Package changed: lxc (Ubuntu) = procps (Ubuntu)
** Also affects: procps (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu
/sysctl.conf | sysctl -e -p - echo pass
** Changed in: procps (Ubuntu Precise)
Assignee: (unassigned) = Stéphane Graber (stgraber)
** Changed in: procps (Ubuntu Utopic)
Assignee: (unassigned) = Stéphane Graber (stgraber)
** Changed in: procps (Ubuntu Vivid)
Assignee: (unassigned
Note that I have a copy of those SRUs already in
ppa:stgraber/experimental if that's useful to someone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1419554
Title:
Can't
Change sent upstream:
https://gitorious.org/procps/procps/merge_requests/37
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1419554
Title:
Can't upgrade procps in LXC 1.1
root@precise-procps:/root# cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sysctl
-e -p - || echo fail
error: Read-only file system setting key kernel.printk
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
error: Read-only file system setting key kernel.kptr_restrict
root@trusty-procps:/root# cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sysctl -e
-p - || echo fail
sysctl: setting key kernel.printk: Read-only file system
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
sysctl: setting key kernel.kptr_restrict: Read-only file system
root@utopic-procps:/root# cat /etc/sysctl.d/*.conf /etc/sysctl.conf |
sysctl -e -p - || echo fail
sysctl: setting key kernel.printk: Read-only file system
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
sysctl: setting key kernel.kptr_restrict: Read-only file system
The verification of the Stable Release Update for mountall has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The same should also be done to the sysvinit script I guess. I'll pick
up those changes in the packaging branch and update for sysvinit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Works fine in an unprivileged container. Thanks!
** Tags removed: verification-needed-trusty verification-needed-utopic
** Tags added: verification-done-trusty verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
All the LXC commands default to tracking a single lxcpath which is
/var/lib/lxc or whatever you set as lxc.lxcpath in /etc/lxc/lxc.conf
It is actually a feature that LXC will not attempt to keep track of
containers outside that path because that's what we expect other
container managers (like
can you paste your /proc/self/cgroup and /var/log/upstart/cgmanager.log?
--
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/1413927
Title:
lxc_cgmanager_enter: 694 call to
You can temporarily turn on vivid-proposed in /etc/apt/sources.list.
lxcfs was released to vivid a couple of hours ago after the latest
cgmanager landed fixing a test regressions due to systemd.
lxc is currently mostly held because of broken apparmor tests.
--
You received this bug
We run the tests using the debian/tests/exercise script in the source
package.
All 3 of your failing tests require connectivity to both the GPG network
and https connectivity to images.linuxcontainers.org, could that be the
problem?
The actual error output from those tests would be useful to
What kernel are you running?
The kernel version reported in this bug report doesn't appear to match
that of an official Ubuntu kernel (currently 3.19.0-15.15).
My best guess here is that your kernel's apparmor implementation is
broken somehow since our own aarch64 tests pass fine.
I'm moving
Public bug reported:
vethXYZ devices as created by LXC shouldn't be managed or even displayed
by Network Manager.
They currently don't appear to be managed (good), but running a few
hundred containers, having each of them take two lines in the network
menu makes NM almost unusable.
** Affects:
Got a slightly better version of the patch. It does a chdir() to fix a
TOCTOU problem.
** Patch added: apport.diff
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1444518/+attachment/4376308/+files/apport.diff
--
You received this bug notification because you are a member of Ubuntu
Attaching an updated diff which should be fixing those two concerns.
** Patch added: apport.diff
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1444518/+attachment/4376695/+files/apport.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
30s to be handled get cancelled (preventing host DoS).
** Affects: apport (Ubuntu)
Importance: Wishlist
Assignee: Stéphane Graber (stgraber)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Good to hear. We did have a bunch of fixes in there which were aimed at
fixing that.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Ah, we have a new lxc and lxcfs currently stuck in vivid-proposed, I
wonder if that'd include the fix you need.
Note that we're still working on fixing a bunch of regressions to allow
those packages to migrate to vivid proper.
--
You received this bug notification because you are a member of
You don't appear to have lxcfs running.
--
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/1441070
Title:
lxc-start on default vivid container fails on apparmor violation
Status
Not anytime soon unfortunately. The backport of all the needed bits as
SRUs will be very very tricky to get right, currently our timeframe is
by 16.04.
If you're maintaining a PPA already, you could pick up the required
trusty packages from ppa:ubuntu-lxc/daily or just include your own
backports
I can confirm that vivid containers using the systemd currently in
proposed now shut down properly.
** 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
I can confirm that unprivileged vivid containers now start properly with
the package from proposed.
** 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
The verification of the Stable Release Update for sysvinit has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Hello Bin, or anyone else affected,
Accepted sysvinit into trusty-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/sysvinit/2.88dsf-
41ubuntu6.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The issue was caused by our auto-backport of LXC and LXD dependencies so
we can guarantee a consistent experience on all Ubuntu releases.
This may indeed cause some occasional breakage when one of those
packages revs their SOVER which is what happened there.
We won't be rebuilding all the
I agree, the stage 2 fix for this issue concerns me with regard to
regressing current use cases.
As much as I'd like to get rid of the rest of this issue (any user of
10.0.4.0/24 behind a router looses connectivity to that subnet), we must
make sure we do not regress anyone who's been relying on
Not sure I like this approach. An init script should never change a
system config, so this is a packaging policy violation...
To be fair, anything we come up with which picks a random/unused subnet
will still break users who may have this subnet in use behind a router,
so that's not really an
Having a special username hardcoded in there seems wrong to me.
Eventually we will want to do proper multi-user on those devices or allow users
to rename the user at which point everything will break again.
What we may consider though is having LXC setup a new lxc-net group with
a matching group
Hello Mike, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.1.4-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I've seen this pretty consistently too across a few hundred containers.
My guess so far was that it had to do with filesystem capabilities or
something similar.
So things are set properly when the image is unpacked by real root on
the host, but the extended attribute then can't be modified from
A pre-start lxc hook with sufficient privileges to start lxc-net would
cover all use cases as far as I can tell and would only require the
addition of two files to the lxc package.
Such a hook would also cover LXD as LXD does exec all LXC hooks, so we
wouldn't even have to mess with those init
Such shuffling around as an SRU seems pretty risky to me. Having the
main lxc package be essentially empty except for the systemd postinst
also feels weird.
This would also further complicate things when I then break lxc into lxc
and lxc-common this cycle (lxc-common will include the apparmor
Pushed to all packaging branches.
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
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/1514942
Title:
lxc-tests no
The lxc-tests package was introduced so that autopkgtest can run all the
LXC tests on upload through the debian/tests/exercise script.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
The behavior of the test is perfectly correct.
This test depends on a CRIU version which can't be found in the Ubuntu
archive and criu itself isn't available on most architectures.
As mentioned in the other bug report, lxc-tests is meant to be used by
autopkgtest through our autopkgtest test
I'll update the package description to make it clear that users aren't
supposed to install that package :)
--
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/1514942
Title:
Just re-read through this whole bug.
It looks like what broke your setup is actually a bugfix in LXC wrt
config inheritance.
Your config contains:
- lxc.mount.auto =
- lxc.mount.auto = cgroup:mixed
This instructs LXC (and that wasn't implemented right at first) to wipe all of
lxc.mount.auto,
Works fine here both privileged and unprivileged, so looks like we fix
this somehow in recent releases. I'll have this issue be closed with the
1.1.5 upload.
** Changed in: lxc (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
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/1502604
Title:
autopkgtests fail in LXC testbed
Status in Auto
Note that newer lxc-checkconfig knows to check for those modules in your
kernel config so it should report what you're missing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
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/1468611
Title:
dnsmasq fails to start in lxc-net
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: lxc (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of
** Changed in: lxc (Ubuntu)
Status: Triaged => 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/1452451
Title:
lxc-attach needs to mount a /proc for
** Changed in: lxc (Ubuntu Precise)
Status: Confirmed => Won't Fix
** No longer affects: lxc (Ubuntu Precise)
** No longer affects: lxc (Ubuntu Saucy)
** Changed in: lxc (Ubuntu Trusty)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
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/1181136
Title:
Empty log file when a container is started with
stgraber@dakara:~/data/code/lxc/lxc$ lxc-start-ephemeral -o blah -d | grep
"lxc-console" | awk '{print $NF}'
blah-psrfp_3s
Not the prettiest thing ever, but definitively doable with current
lxc-start-ephemeral.
I won't be spending more time on lxc-start-ephemeral though as we'll have the
new
** Changed in: lxc (Ubuntu Wily)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu Xenial)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
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/1424143
Title:
lxc-net should attempt to use ip before
** No longer affects: lxc (Ubuntu)
--
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/1439649
Title:
Pacemaker unable to communicate with corosync on restart under lxc
Status in
stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ lxc-stop -n foo ;
lxc-destroy -n foo ; lxc-clone clean-machine foo
foo is not running
Container is not defined
Error: container clean-machine is not defined
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received
** Package changed: lxc (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1496877
Title:
apparmor profile fails to load in Ubuntu 15.04
** Changed in: lxc (Ubuntu)
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/1458173
Title:
Vivid + LXC autostart not working
** Changed in: lxc (Ubuntu)
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/1414771
Title:
Can not clone lxc container with lvm
** Also affects: lxc (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Not seeing anything obviously wrong here...
To rule out a few more things, when you get the hanging "lxc-stop -n container
-k", can you do and paste the output of:
- ps faux
- dmesg
Thanks!
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: lxc (Ubuntu)
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Medium => Wishlist
--
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/1475751
- What Ubuntu version are you using?
- What LXC version are you using?
- Is the container privileged or not?
- Where did you see this behavior (over ssh to the container, in a lxc-console
shell or in lxc-attach)?
That should help figure out what's going on a bit more.
** Changed in: lxc
Closing this, we don't have any Ubuntu release with supported VZ anymore
(last was hardy).
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
We're not going to fix this in LXC as the failure is obviously intended.
However with lxcfs we can now render /proc/swaps in a more consistent
way, including hiding swap for containers which shouldn't have any swap
access.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
--
*** This bug is a duplicate of bug 1182458 ***
https://bugs.launchpad.net/bugs/1182458
** This bug has been marked a duplicate of bug 1182458
ubuntu-cloud template: use simplestreams to add integrity verification
--
You received this bug notification because you are a member of Ubuntu
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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/1471358
Title:
lxc-checkconfig shows Mainline PPA
1 - 100 of 758 matches
Mail list logo
