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
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
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
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.
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
-
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
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
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
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
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
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
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
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
(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
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
** 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
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: 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
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 => 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 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/1522992
Title:
/usr/bin/lxc-
stop:11:strlen:prune_init_scop
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
@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
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
** 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
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: 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
** 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
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: 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/
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
--
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
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
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
** 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
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
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
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
** 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
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
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
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
** 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
** 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
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
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
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
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
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..
The cpuset "error" is normal, it just means the directory was already
there and is getting recycled. The boot_id permission problem has
already been fixed upstream.
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of U
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
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/1888705
Title:
lxc ftbfs against libseli
We'll want that sudo fix included in Ubuntu.
It's the usual catch with unprivileged containers only being able to
lower their limits and never raise them so there's nothing we can really
do about it in LXD.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notif
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
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/1884635
Title:
lxc 1:4.0.2-0ubuntu1 ADT
All LXD virtual machines are hitting this too.
Run:
- lxc launch images:ubuntu/focal/cloud f1 && lxc console f1
And you'll see it show that message. As mentioned above, boot then still
goes ahead and you get a login prompt, but as that may not always be the
case.
For example in linux-kvm, that
How are you logging in and can you confirm that this path does hit libpam_cgfs?
Also look in /var/log/auth.log for potential errors.
--
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/bug
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
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/1668049
Title:
lxd cannot shutdown container
Status in s
There is no /sys/fs/cgroup/unified on xenial, closing.
** Changed in: systemd (Ubuntu Xenial)
Status: Incomplete => Invalid
--
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/
** No longer affects: apparmor (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
--
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/1645037
Title:
apparmor_parser hangs i
Is this still an issue?
--
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/1668049
Title:
lxd cannot shutdown container
Status in systemd package in Ubuntu:
New
Bug descri
I've not seen this issue in quite a long time at least on bionic/focal,
so will tentatively mark it as fix released. If someone still hits this,
please tell us on what release and we'll add some SRU tasks.
** Changed in: binfmt-support (Ubuntu)
Status: Confirmed => Fix Released
** Changed
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
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/1634199
Title:
In 16.10, LXD won't work with enforced d
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: apparmor (Ubuntu Xenial)
** No longer affects: apparmor (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Changed in: layer-snap
Status: New => Invalid
--
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/1709536
Title:
snapd 2.26.14 on ubuntu-core won't start in container
Yes, different versions of different distros will have different
behavior as to what they do with pre-existing network config. Point is,
it's racy and unreliable, the only way to get guaranteed behavior is to
make sure that nothing else attempts to manage the network when you've
already pre-configu
LXC always does the same thing, it preconfigures your network namespace.
Now if the OS you're running in the container runs its own network
configuration tool, that pre-made configuration will likely get reset or
mangled.
If you want to use those config keys, you need to make sure you're not
runn
The main leak was in dqlite and has now been included in master, the
next rebuild of the snap (likely later today) will include it.
** Changed in: lxd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
https://github.com/lxc/lxd/pull/7167
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Status
https://github.com/canonical/raft/pull/123
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
S
Ok, can you post the output of "ls -lh /proc/PID/fd/" where PID is the
PID of the "lxd --logfile ..." process and the PID of the "daemon.start"
script (lxd's parent process)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm
Can you show `lxc info` please as well as `ls -lh /proc/self/fd` inside
that "reproducer" container?
I just tested it here and I'm seeing:
```
root@bionic:~# ls -l /proc/self/fd
total 0
lrwx-- 1 root root 64 Apr 9 20:57 0 -> /dev/pts/1
lrwx-- 1 root root 64 Apr 9 20:57 1 -> /dev/pts/1
l
Considering fixed as we now have 4.0.1 in the archive, if this still
happens, let us know.
** 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://
This has already been fixed in 4.0.1-0ubuntu1
** 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/1870539
Title:
pac
Wrong package as that's against the LXD snap and not any archive
package.
The issue sounds like: https://github.com/lxc/lxd-pkg-snap/issues/39
If you have any idea on how to reliably reproduce the issue, please
comment in the Github issue as it's something we'd really like to get
rid of...
** Bu
This is now fixed in all channels and our own validation now checks for
this too.
** 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.laun
The release announcement finally got pushed out here:
https://discuss.linuxcontainers.org/t/lxc-4-0-lts-has-been-released/7182
The main new features are:
- cgroups: Full cgroup2 support
- cgroups: Freezer support in CGroup2
- cgroups: eBPF device controller support in CGroup2
- config: Add lxc
Hmm, I thought we pushed all the nesting fixes to stable on Friday. Our
own nesting tests are all clean but it's possible we're not hitting this
particular exec case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubun
** Changed in: lxc (Ubuntu)
Status: Incomplete => 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/1659590
Title:
containers won't start after lxc and apparm
There's nothing particularly safe for us to do here out of the box.
Using an alternative profile or appending to the profile (in LXD's case) is
your best bet.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
** 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/1389954
Title:
Make .lxc domain name resolution easier to discov
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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/1569679
Title:
lxc failed to do lxc-checkpoint again
Status in
** 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/1240757
Title:
Bridge not created if bind9 is on
Status in bind
** 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/1861880
Title:
lxc-attach command does not return error exit cod
** 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/1858799
Title:
lxc ADT test failure on Bionic with linux-raspi2-
** 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/1866124
Title:
ps -eo lxc no longer shows a task's lxc container
Stat
anyone still affected by this?
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1659590
Title:
containers won
We're now using distrobuilder to build pre-made images avoiding the mess
that was those scripts.
** 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 Ubun
It's not currently failing based on recent logs anyway.
** 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/1776381
Title:
*** This bug is a duplicate of bug 1837537 ***
https://bugs.launchpad.net/bugs/1837537
** This bug has been marked a duplicate of bug 1837537
FTBFS since lxc has different version numbers in Debian and Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch s
Hmm, no, that would be wrong.
Wants=/Requires= would cause lxc-net to not start if network-
online.target is missing or if it fails. We only want to start after it
if it does exist, which is what After does.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug n
What are your subuid/subgid allocations like?
** 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/1840639
Title:
Versi
There is configurable prompting for those that want it. We also refuse
to delete running containers.
** 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
1 - 100 of 759 matches
Mail list logo