Have confirmed the packages to be functional on both focal and impish.
Tried installation, upgrade and basic container creation, deletion and normal
operations.
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish
-
We've fixed those upstream already and will be in the next upstream
point release.
--
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/1987625
Title:
lxc: FTBFS against glibc 2.36.
We don't track snap bugs on Launchpad, nor is this something we can fix
as it's indeed a missing feature of snaps. If snapd ever grows support
for landing manpages on the system (similar to what it does with bash
completion profiles), we'll be able to use our manpage generate showed
above to popula
This was definitely a mistake made when preparing the original LXC 5.0
snapshot for upload in Ubuntu.
LXC_DEVEL=1 should only ever be set when dealing with current snapshots of the
upstream codebase.
Shipping an older snapshot with LXC_DEVEL=1 set will cause any tool that
consumes liblxc and whi
My two cents here are that we should:
- Rapidly fix the LXC_DEVEL situation across all supported Ubuntu releases.
- Separately prepare a new package for noble which performs the Debian merge
and introduces the needed transitional packages to get users from the current
Ubuntu-specific naming ove
Moving to Triaged, LXC does have a comprehensive autopkgtest test suite
which runs both unit and integration tests and is integrated with
Ubuntu.
** Changed in: lxc (Ubuntu Focal)
Status: Incomplete => Opinion
** Changed in: lxc (Ubuntu Focal)
Status: Opinion => Triaged
** Changed
https://autopkgtest.ubuntu.com/packages/l/lxc
--
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/1923232
Title:
SRU of LXC 4.0.6 to focal (upstream bugfix release)
Status in lxc
Hello Serge, or anyone else affected,
Accepted lxc into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1:4.0.6-0ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Uploading a LXD SRU to bionic with the one commit cherry-picked shouldn't be
too hard.
But we'd need someone to sort out the SRU paperwork as I have no idea how we'd
even test the fix.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you a
Okay, that looks promising. Can you add the SRU sections to the
description describing those testing steps? Then I can upload to the SRU
queue referencing this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ub
Uploaded to the queue
** Changed in: lxd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
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/1959047
Title:
systemd ign
Public bug reported:
LXC 5.0 LTS will very soon be released.
The upstream release has been held up due to an incomplete port to meson (and
deprecation of autotools), it's otherwise been ready to go for a few months.
As far as LXC releases go, it's a very light one. Comparing it to
current 4.0.12
** Changed in: lxc (Ubuntu)
Status: New => In Progress
--
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/1957934
Title:
error in man page for lxc.container.conf
Status in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=591a22c14d3f45cc38bd1931c593c221df2f1881
** 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
Marking as invalid as this wasn't an LXC bug but a kernel bug.
--
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/1931064
Title:
lxc autotest failure with kernel >= 5.13
Status i
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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.
https://bugs.launchpad.net/bugs/1917601
Title:
lxc 1:4.0.4-0ubuntu3 ADT test failure with linu
The error you're getting is coming from systemd in the container which
for some reason is trying to mount a cgroup1 hierarchy rather than using
cgroup2 like the rest of your system.
You may be able to workaround that by using `lxc.init_cmd` to pass
/sbin/init with additional arguments to change th
Seems green lately
** Changed in: lxc (Ubuntu)
Status: New => 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/1916669
Title:
autopkgtests flaky for hirsute
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: libnih (Ubuntu)
Status: Confirmed => 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.
https://bugs.launchpad.net/
Are we still seeing this?
The failure looks a lot like it could be a legitimate kernel issue.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu Focal)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** 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.
https://bugs.launchpad.net/bugs/1887919
Title:
autopkgtest failure with libselinux 3.1
Status in glib
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Released
** Changed in: lxc (Ubuntu Bionic)
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.launchp
Did we ever see this one again or was it just transient?
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
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/1881292
Tit
** 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.
https://bugs.launchpad.net/bugs/1883041
Title:
libpam-cgfs fails to create freezer cgroup writable by
CRIU is once again in the archive (Ubuntu is just following what's in
Debian for this one).
** 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.
h
** 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/1646462
Title:
lxc-create cannot setgid
Status in lxc:
F
Could you recheck with the current LXC (4.0.12) as the cgroup code was
reworked quite extensively.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubun
@brauner do you know what's the state of quotas in a VFS idmapped
shifted world?
--
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/1515615
Title:
Disk quotas don't work in LXC co
Moving over to the kernel as a userspace process shouldn't be able to
cause such a hang regardless of what it does so this looks like a kernel
bug (lock related by the looks of it).
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member
Closing as it's not really LXC's job to try and change that one.
These days we'd recommend distros to change default permissions or
ideally get that changed at the kernel level. Short of that, we do have
some documented recommendations in our production environment doc for
LXD: https://linuxcontai
** 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/1522992
Title:
/usr/bin/lxc-
stop:11:strlen:prune_init_scop
Closing the LXC side of this bug as there's nothing we can really do here.
It's either a kernel issue (needs support for their socket option within a
network namespace) or an open-iscsi issue where they could have some kind of
fallback mechanism.
** Changed in: lxc (Ubuntu)
Status: Confir
Ubuntu Touch hasn't been a thing for a few years and UBPorts hasn't
really been hitting this issue as far as I know.
** 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
** 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/1591124
Title:
LXC: Cannot create a container with the specif
Closing as these days we only have LXD preinstalled on those images and
LXD does a lot more validation and only creates the networks on first
use.
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** 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.
https://bugs.launchpad.net/bugs/1502604
Title:
autopkgtests fail in LXC testbed
Status in Auto
I think the strlcat thing is a red herring or an indication that the
test environment is somehow in a bad shape. This could be explained if
there was two versions of liblxc on the system for example.
Outside of that, I'm also seeing:
```
lxc-start tmp.KEpxw2rh0e 20220205081512.354 ERRORutils
** Changed in: lxc (Ubuntu)
Status: Incomplete => Invalid
** Changed in: lxc (Ubuntu Focal)
Status: Incomplete => Invalid
** No longer affects: lxc (Ubuntu)
** No longer affects: lxc (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Touch see
In general, it's indeed a problem for such cases, though there are a few
mitigating factors here:
- This would only be a problem for those who upgrade from focal to
impish. My understanding is that there is no direct upgrade path to
achieve this, you'd need to go throughgroovy and hirsute, both o
(We technically had the same issue with the previous upload as 4.0.6 was
higher than what hirsute shipped at the time, though in that case the
EOL for hirsute was just a month or so away making the case for skipping
that SRU even stronger :))
--
You received this bug notification because you are
Marking this invalid against LXC as the code in the archive for package
testing is handling this case properly already.
--
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/1960847
Ti
The autopkgtest script in the Ubuntu package has:
# Skip some tests due to cgroup v2 incompatibility
if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then
[ "$testbin" = "lxc-test-apparmor-mount" ] && \
ignore "$STRING" && continue
[ "$testbin" = "lxc-tes
Thanks Brian, my memory of this whole thing clearly dates back a long
time then ;)
I still remember some of the discussions of what we'd expect people to
be doing in such cases and whether we'd ever officially support (as in
test/validate) upgrade paths other than release to release+1 and LTS to
L
Uploaded the exact same thing to impish queue.
--
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/1959993
Title:
SRU of LXC 4.0.12 to focal (upstream bugfix release)
Status in lx
Privileged containers have a much stricter apparmor policy applied than
unprivileged containers.
That's because unprivileged containers primarily rely on the user namespace to
prevent breakout and taking over of the host whereas privileged containers rely
entirely on apparmor.
As apparmor isn't
If this only fails in privileged containers, then I probably wouldn't
worry about it too much, those aren't the default and a LOT of things
break in privileged containers, so I don't think it's worth doing distro
changes to accommodate this, assuming the container otherwise still
boots.
For cases
Closing the LXD task as there's not really anything we can do there.
The options here are pretty much:
- Do nothing, if it's just privileged containers, it's usually not a big deal
- Significantly rework apparmor mount handling logic and policies so this can
be safely allowed
- Ship unit overr
Can you show `cat /proc/self/mountinfo` on your host?
--
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/1915091
Title:
Nautilus shows LXD storage pool in sidebar
Status in lxc p
Hmm, LXD's mounts are in a separate mount namespace invisible from the
host, so I don't quite get how this is possible ;)
--
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/1915091
Ok, so the mount table output confirms that your LXD default storage
pool isn't visible in the host's mount table, so that's not what's
triggering nautilus.
Also, if that was the case, I'd have seen it on my own machine a long
time ago ;)
My best guess is that it's the loop device (also called de
Making /sys read-only will break very very many things that we have no
intention of breaking.
LXD is also completely init system agnostic and we have no idea what the init
system in a particular container may be.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bu
This is a systemd/udev bug. We're aware of the CONTAINER_INTERFACE and
it being wrong doesn't mean we need to change LXD to make it similarly
wrong.
LXD containers need to have udevd running to function properly, so you'll need
to undo that change.
If there is a bug in how udevd now behaves, that
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Ubuntu containers team (ubuntu-lxc)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Changed in: systemd (Ubuntu)
Assignee: Ubuntu containers team (ubuntu-lxc) => Christian Brauner
(cbrauner)
--
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/1914062
Ti
Christian submitted https://github.com/systemd/systemd/pull/18559 which
got turned into https://github.com/systemd/systemd/pull/18684 and has
now been merged in upstream systemd.
We've both tested the resulting systemd and can confirm that /run/udev is now
properly populated.
Please cherry-pick t
Now that we have the 5.8 kernel in HWE for focal, all my servers are
hitting this, both on metal and in containers. This causes things like
"systemctl show" to show an error as well as partial data.
It really feels like this should have been fixed before the rollout of
the 5.8 kernel through HWE..
** 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/1937945
Title:
old gpg keyserver no longer works
Status in
The upstream announcement is now available here:
https://discuss.linuxcontainers.org/t/lxc-2-0-11-has-been-released/4238
--
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/1816642
Uploaded to the SRU queue for Ubuntu 16.04 LTS.
--
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/1816642
Title:
SRU of LXC 2.0.11
Status in lxc package in Ubuntu:
Fix Release
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
--
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/1813622
Title:
systemd-resolved, systemd-networkd and other
** Changed in: lxc (Ubuntu Xenial)
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/1788457
Title:
SRU of LXC 3.0.2 (upstream bugfix relea
Public bug reported:
LXC upstream released LXC 3.0.3 as a bugfix release with following
changelog:
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style i
Uploaded to disco, will wait for autopkgtest to be happy before I start
pushing the SRUs.
** Changed in: lxc (Ubuntu Xenial)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Bionic)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed i
Uploaded to cosmic
--
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/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix release)
Status in lxc package in Ubuntu:
Fix Released
St
And the bionic version too
** Changed in: lxc (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: lxc (Ubuntu Cosmic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc
This system is using a mix of -proposed and non-proposed packages, this
isn't going to work and isn't supported, marking invalid.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
Well, the adt setup in this case just can't work, you can't tell apt to
install lxc-utils from -updates and liblxc1 from -proposed when they
have strict dependencies between them, you're just going to be getting
an apt failure.
--
You received this bug notification because you are a member of Ubu
We never had any other report of this so it's not a generic issue in
libpam-cgfs, this suggests a debconf issue, so closing the lxcfs task.
** Changed in: lxcfs (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Updated a bionic and cosmic system, containers kept working fine, newly
started ones are good too.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this
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 regr
** Changed in: lxc (Ubuntu Xenial)
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/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix relea
"lxc.cgroup.devices" is meaningless for unprivileged containers as those
can never create those devices anyway, so they'll only ever have access
to whatever devices lxc provides and nothing more. All our own default
configs specifically do not set that cgroup controller for unprivileged
containers.
/dev/.lxc/* shows up when nesting is enabled, so that's indeed related
to the change Adam did.
--
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/1845337
Title:
Disco autopkgt
Looking at the linked reports, it sounds like either
/dev/network_latency doesn't exist in those systems (which would differ
from standard kernel behavior on Ubuntu), or there is a legitimate issue
with injecting that device afterwards.
In either case, likely to be a kernel config change or a kern
Moving this bug to the kernel as investigation discovered a kernel regression
in overmounting protection behavior in 5.3 rc1.
So not a LXC bug but a kernel one.
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this b
Public bug reported:
iptables just got replaced by the nftables wrappers, effectively
changing all Ubuntu systems to using nftables rather than regular
iptables/ip6tables/ebtables.
Unfortunately those wrappers aren't perfect and don't convert every
option properly, nor know about some of the avai
Ah, that's good to know and we should definitely aim at refreshing
nftables prior to doing any amount of testing on the wrappers.
The failure I've seen for LXD specifically was around complex protocol
parsing (IPv6 router advertisements I believe) through ebtables, so not
a very usual thing to do,
This is a LXD commit, not a LXC one. LXC cannot be fixed in the same way
as it has a single apparmor policy covering both privileged and
unprivileged containers, until such time as the apparmor security issue
is resolved, there's nothing we can do to fix this issue without causing
a giant security
*** This bug is a duplicate of bug 1641236 ***
https://bugs.launchpad.net/bugs/1641236
** This bug has been marked a duplicate of bug 1641236
Confined processes inside container cannot fully access host pty device
passed in by lxc exec
--
You received this bug notification because you ar
Public bug reported:
LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog
for both of them can be found below:
LXC 2.0.10:
- tools: allow lxc-attach to undefined containers
- utils: move memfd
We'll have to make that 2.0.11 as unfortunately the 2.0.10 release
tarball is bad, waiting for the new release to unblock this bug.
** Changed in: lxc (Ubuntu Trusty)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Xenial)
Assignee: (un
Yes, it was removed on purpose, nothing in the archive depended on it
except for the autopkgtests for LXC which now just build the test
binaries as needed.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch see
Just run autopkgtest against the lxc 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/1758255
Title:
lxc-tests package is not available in Bionic
Status in lxc package
This has been fixed upstream and in Ubuntu 18.04, marking fix release.
If we do a SRU of 2.1.1 for Ubuntu 17.10, this fix will be in it.
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I'd like to +1 what cyphermox said, the expected behavior on Ubuntu is
that if you do receive a RA, you let the kernel configure it.
That's how Ubuntu has been ever since IPv6 support was enabled and I
personally have about 200 systems that very much rely on this (no
specific IPv6 configuration, j
nge included in this upstream release.
Once the SRU hits -updates, we will be backporting this to xenial-
backports as well, making sure we have the same version everywhere.
** Affects: lxc (Ubuntu)
Importance: High
Assignee: Stéphane Graber (stgraber)
Status: Fix Released
** Affe
** Summary changed:
- SRU of LXC 3.0.1
+ SRU of LXC 3.0.1 (upstream bugfix release)
--
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/1775283
Title:
SRU of LXC 3.0.1 (upstream b
Just performed a basic check here with a number of containers running,
upgrading and confirming that they're all still running and can be
interacted with just fine.
Marking as confirmed.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-
Can you run:
lxc-create -n gym -o lxc.debug -l DEBUG -t download -- -d ubuntu -r xenial -a
amd64
And attach the "lxc.debug" file?
--
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/bu
** Changed in: lxc (Ubuntu Xenial)
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/1775283
Title:
SRU of LXC 3.0.1 (upstream bugfix relea
** Also affects: ust (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: ust (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: ust (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are
It's in 17.10
** 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/1699759
Title:
LXC Alpine template broke
Hello Michael, or anyone else affected,
Accepted ust into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ust/2.7.1-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Hello Michael, or anyone else affected,
Accepted ust into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ust/2.9.0-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Michael, or anyone else affected,
Accepted ust into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ust/2.9.1-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Marking the lxc task as invalid since LXC does not drop any such
capabilities by default, so such failure isn't lxc's fault. It's either
the user's fault (by dropping capabilities that Ubuntu/Debian consider
as required) or the systemd's package fault (for not doing a capability
check).
** Changed
I think we have that fix in liblxc 2.0.9 which still needs SRUing to the
various Ubuntu stable releases.
--
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/1692111
Title:
Unable t
Yeah, that's a network issue, bouncing it usually makes it pass
eventually.
http://autopkgtest.ubuntu.com/packages/l/lxc/trusty/amd64 shows recent
success there.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
To
Removed this SRU from -proposed.
Two reasons for this:
1) The mentioned regression
2) We should NEVER introduce a new dependency to a package through an SRU.
Doing so will prevent any user that doesn't dist-upgrade (uses
upgrade/safe-upgrade instead) from getting the new dependency, instead
Graber (stgraber)
Status: In Progress
** Affects: lxc (Ubuntu Xenial)
Importance: High
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxc (Ubuntu Bionic)
Importance: High
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects
1 - 100 of 759 matches
Mail list logo
