promoted to main
** Changed in: golang-github-mattn-go-colorable (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-mattn-go-colorable in
Ubuntu.
promoted to main.
** Changed in: golang-github-mattn-go-isatty (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-mattn-go-isatty in
Ubuntu.
it hasn't
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to charm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1546776
Title:
[FFe] charm-tools 2.0
To manage notifications about this bug go to:
Those errors are typically caused by a bad mirror or a caching proxy on
your network and aren't caused by the package themselves.
** Changed in: cgmanager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Curtis: can you paste a log to confirm it's the same issue as Colin?
It looks like some of the cgroup:mixed logic recently introduced in
cgfsng (to match that of the old cgfs backend) is a bit wrong here and
attempts to create a cpu/cpuset,cpuacct symlink instead of symlinking
cpu to
Serge is out today actually, I'll try to take a look.
--
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/1559169
Title:
containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
To
Could be that we somehow fixed a bug where the failure to run the script
wasn't considered fatal before but is now.
Anyway, sounds like the error you were getting makes sense to me so
closing this as invalid (not a bug).
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received
Unfortunate that this only gets in so late in the cycle, but I can
certainly see the benefit of updating this before we have to support it
for 5 years.
Testing seems reasonable. debdiff is unreviewable so we can only rely on
the testing...
Assuming that you'll take care of any yet unknown
Your container appears to have an autodev hook script configured and
that script failed to run.
** Package changed: lxd (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
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/1559169
Title:
containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
To
Ok, cool, that confirms it's the same thing.
--
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/1559169
Title:
containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
To manage
Ok, I'm assuming you meant "2.0 alpha" in the updated description.
Anyway, sounds fine to me, approved.
** Changed in: maas (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Can you talk a bit about your rdepends and how they'll be impacted with
this change?
Also, what's your testing story for Ubuntu package?
You're asking for a standing FFe which I suspect means we'll be getting
a bunch of uploads of MAAS, when do you expect the first upload to
happen and what
Update init script is: http://paste.ubuntu.com/15264484/
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
To manage
That part of the init script looks just plain wrong to me... I'm
guessing the intent was for /dev/cpuctl to be a bind-mount of
/sys/fs/cgroup but that's not at all what the code does.
I'll update my local copy here to replace that by a simple symlink from
/dev/cpuctl to /sys/fs/cgroup/cpu
--
I have a debdiff ready to upload for the changes so far but will wait
until we figure out the rest of this issue.
Serge Hallyn is also working on a cgroup-lite changes to get us rid of
most of that diff too.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
That is very weird, the cgroup-lite upstart job should result in your
case in 4 cgroup mounts, so I'm not sure why it's not happening here...
Could you run "bash -x /bin/cgroups-mount" as root and post its output
including a dump of /proc/self/mountinfo before and after running it?
that should
So far that does seem to confirm the hypothesis that since the phone has
systemd installed (but unused), this meets lxc's dependency on systemd |
cgroup-lite but as upstart is used to boot and upstart itself doesn't
mount the cgroup controllers, this results in a system without cgroups
mounted.
Some more information on cgroup-lite and where it may fail.
- cgroup lite is triggered on "mounted MOUNTPOINT=/sys/fs/cgroup" => the path
is shown as mountend above, so not it
- The job then gets skipped if /bin/cgroups-mount doesn't exist => part of the
cgroup-lite package, so not it
- The
That mountinfo shows no mounted cgroup controller, hinting that cgroup-
lite didn't start or otherwise failed to start.
Could you look for a /var/log/upstart/cgroup-lite.log file?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Do you know if the phone actually uses systemd as its init system
nowadays?
LXC requires either systemd or cgroup-lite to mount all the cgroup bits
properly, if systemd is installed but not used, that could explain what
you are seeing. Installing cgroup-lite should have fixed it though,
unless
We're gonna need a /proc/self/mountinfo output if we want to figure out
what the controller #7 is on your system...
--
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/1551150
Title:
Can you paste the content of /proc/mounts on such a system and confirm that
either one of those is true:
- systemd is installed and used as init system
- cgroup-lite is installed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
That's very weird, all my xenial test systems show lxc-container-
default-cgns in the apparmor_status output
--
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/1549363
Title:
Unprivileged
Hmm, does /etc/init.d/apparmor reload fix the profile not being loaded?
We've not been introducing new profiles very often and those profiles
are loaded through apparmor includes so I can certainly see a standard
dh_apparmor being confused by it and not reloading everything properly
on upgrade.
As for the cgroups, we've noticed at least one issue in the cgfs logic
of LXC which was fixed earlier today, the package is still going through
QA (currently in proposed), should make it to the release pocket within
a couple of hours.
The fix was specifically to fix unprivileged but root-owned
)
Status: New => Won't Fix
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: juju-core (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
** No longer affects: lxd (Ubuntu)
--
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/1544157
Title:
lxc exec not working in xenial
To manage notifications about this bug go to:
I'm unfamiliar with the squid codebase but if it does use the normal
socket library, it would be doing a getaddrinfo, then iterate over the
results, those results would begin with IPv6 records as IPv6 is
always to be preferred over IPv4 when available, but any attempt to
connect would result
** Package changed: squid (Ubuntu) => squid3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1547640
Title:
proxy tries ipv6 and gets 503 when no ipv6 routes
To manage
Not much we can do about the IP address though. For the MAC it's
unlikely that anything in the container is tied to it so we can just
generate a fresh one without requiring any knowledge about the workload
or the environment.
An IP address is much more problematic because maybe you did mean to
** Project changed: lxc => lxc (Ubuntu)
--
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/1359224
Title:
Feature request: Add support for multiple bridges
To manage notifications about
** Project changed: lxc => lxc (Ubuntu)
--
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/1428490
Title:
AppArmor vs unix socket inside LXC containers
To manage notifications about this
** Project changed: lxc => lxc (Ubuntu)
--
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/1302053
Title:
lxc-start with bad container name gives strange err message
To manage
** No longer affects: lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1340836
Title:
error: error executing "lxc-start" when juju client runs inside kvm
To manage
** Project changed: lxc => lxc (Ubuntu)
--
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/1441307
Title:
lxc-clone makes new copies of each hardlinked file
To manage notifications about
** Project changed: lxc => lxc (Ubuntu)
--
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/1470599
Title:
Stuck mountall inside container
To manage notifications about this bug go to:
** Project changed: lxc => lxc (Ubuntu)
--
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/1436722
Title:
lxc domain setup instructions are incorrect
To manage notifications about this
** Project changed: lxc => lxc (Ubuntu)
--
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/1472929
Title:
undefined symbol: cgmanager_get_pid_cgroup_abs_sync
To manage notifications about
** Project changed: lxc => lxc (Ubuntu)
--
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/1445539
Title:
Can't create vivid lxc on trusty
To manage notifications about this bug go to:
** Project changed: lxc => lxc (Ubuntu)
--
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/1486073
Title:
'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7
To manage
** No longer affects: lxc
--
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/1342960
Title:
comments in common.conf must be updated
To manage notifications about this bug go to:
** Project changed: lxc => lxc (Ubuntu)
--
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/1521151
Title:
init: lxc-instance main process terminated with status 255
To manage
** Project changed: lxc => lxc (Ubuntu)
--
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/1532069
Title:
Can't create a container with a loop backing store in 1.0.8
To manage
** No longer affects: lxc
--
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/1285850
Title:
interuppting lxc-clone can destroy source container
To manage notifications about this bug go
Nothing LXC can do about it. An unprivileged container cannot have any
more right than the user which spawned it. Your user cannot open that
many files therefore root in the container can't either.
** Changed in: lxc
Status: New => Won't Fix
--
You received this bug notification because
That's in favor of LXD.
All LXC code from JuJu has been or is in the process of being rewritten
to use LXD instead.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
** Changed in: lxd (Ubuntu)
Status: Triaged => Fix Committed
** Package changed: lxd (Ubuntu) => lxc (Ubuntu)
--
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/1537939
Title:
** Package changed: lxc (Ubuntu) => lxd (Ubuntu)
--
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/1544157
Title:
lxc exec not working in xenial
To manage notifications about this bug go
Up until last week, cloud images were being built just fine with lxc and
lxd in them, starting this week, they fail, that seems like a regression
to me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I just compared the content of lxc 1.1.5-0ubuntu6 which I'm assuming was
the last working LXC version in cloud images and lxc
2.0.0~beta2-0ubuntu2 that we have now and neither provides any
/etc/init.d script nor am I seeing any packaging change on our side
which would explain this.
Packaging diff
I'm marking the lxc task invalid as no packaging change occurred on
lxc's side and this, admittedly rare, init script configuration has been
supported for years and should still be supported.
Directly subscribing the containers team though so we can help track
down the source of the regression.
Subscribing Martin Pitt who very recently merged init-system-helpers.
I've not yet read the diff, but this seems like a fair bet as to what
changed recently (last upload was Feb 5).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
** No longer affects: lxd (Ubuntu)
--
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/1527374
Title:
privilege escalation on attach through ptrace
To manage notifications about this bug
Sounds like a lxcfs or cgmanager issue, moving to lxcfs for now.
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
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/1527666
Title:
lxc
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1518440
Title:
tgt fails to install in LXD
To manage
Oh, yeah, it definitely shouldn't fail on oom_adjust. I remember we had
to patch a few things because of that kind of stuff before.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1518440
So the right thing to do when writing to oom_score is:
- Try oom_score_adj first if it doesn't exist, silently fallback to oom_adj
- Don't fail if the file doesn't exist
- Don't fail if write gets you EACCESS
- Fail for all other return values
** No longer affects: lxd (Ubuntu)
--
You
Moving this one over to LXC, a quick look at the code (thanks Serge)
seems to indicate that we only support personalities with seccomp for
x86 and power. A similar code path must be added for arm on aarch64.
** Changed in: lxd (Ubuntu)
Status: New => Triaged
** Changed in: lxd (Ubuntu)
Martin: that won't work.
You can't change endianness in a chroot, only in a VM.
So if you have a ppc64eb system (commonly known as ppc64), then you can
have a ppc32eb (commonly known as powerpc) chroot or container.
But you cannot have a ppc32eb or ppc64eb chroot or container on a
ppc64el
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
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
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
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
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
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
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
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
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
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
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
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
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
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
** Changed in: lxc (Ubuntu Vivid)
Status: In Progress => Fix Released
** Changed in: lxc (Ubuntu Wily)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
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/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to
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
apport says that something on your system removed
/etc/init/cgmanager.conf and /etc/init/cgproxy.conf which then caused
that upgrade error.
** Changed in: cgmanager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Closing as won't fix since the error tracker is basically unusable right
now and we've never had a single other report of this despite having
cgmanager on a lot of armhf devices now (Ubuntu Core & Ubuntu Phone).
I also went to look at my armhf builders for LXC where we spawn about
200 cgmanager
lxc-stop didn't, upstart in your container did.
lxc-stop sends SIGPWR to the container's PID 1, in your case, upstart.
As Serge pointed out, using --share-net means that the upstart tools int
the container interact with upstart on the host.
As a result, the shutdown sequence in the container
Because it's needed for things like the Android container on Ubuntu
Touch, application containers on OpenWRT, ...
There are legitimate use cases for those features, those use cases just
never apply when running a full Linux distro inside the container :)
LXC used to default to sharing the netns
Great. Current plan is to release the SRUs on Monday, I figured
releasing them over the thanksgiving weekend wouldn't be the best idea.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
When did you last reboot this system?
Also, does rebooting and then upgrading again solve it?
The most likely cause for this is a network manager bug that destroys
lxcbr0, this was fixed in Network Manager a few weeks back but does
require you to have rebooted your system after applying those
** 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.
https://bugs.launchpad.net/bugs/1503330
Title:
New upstream bugfix release 1.1.4 (LXC MRE)
To
** 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.
https://bugs.launchpad.net/bugs/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to
** 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.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage
** 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.
https://bugs.launchpad.net/bugs/1515463
Title:
Broken juju LXC deployments
To manage notifications
** 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.
https://bugs.launchpad.net/bugs/1510619
Title:
Wily: add machine fails using kvm and lxcbr0
To
Brad: any chance you can confirm this works as expected?
--
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/1515463
Title:
Broken juju LXC deployments
To manage notifications about this
** 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.
https://bugs.launchpad.net/bugs/1516971
Title:
LXC's preserve_ns fails on < 3.8 kernels
To manage
** 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.
https://bugs.launchpad.net/bugs/1514623
Title:
New upstream bugfix release 1.0.8 (LXC MRE)
To
** 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.
https://bugs.launchpad.net/bugs/1429140
Title:
lxc-net upstart script fails on nonexistent iptables
** 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.
https://bugs.launchpad.net/bugs/1466458
Title:
template 'none' doesn't work with lxc-create
To
** 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.
https://bugs.launchpad.net/bugs/1441068
Title:
lxc-destroy fails on btrfs subvolumes
To manage
** 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.
https://bugs.launchpad.net/bugs/1497420
Title:
systemd 226 (moving pid 1 into /init.scope cgroup)
Fix pushed to the lxc packaging branch.
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/1519228
Title:
Drop obsolete
** Changed in: lxc (Ubuntu Xenial)
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/1517107
Title:
$PATH is getting clobbered when starting a
** Description changed:
- I have a script using the Python3 LXC API that starts up a container.
- If I use an Upstart job to call the script, the $PATH env var is getting
- clobbered and the container fails to start.
+ == SRU ==
+ Rationale: LXC 1.1 and higher mangles the process env to be able
** Changed in: lxc (Ubuntu)
Status: New => 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/1514960
Title:
lxc-test-checkpoint-restore fails with no explanation why
To
** Also affects: lxc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Wily)
Importance:
1 - 100 of 914 matches
Mail list logo
