FYI, reproduced this in LXD virtual machines trying to use UEFI HTTPBOOT.
Similar setup, http-only (no https yet) and no secureboot enabled.
Shim and grub are both retrieved properly over http, then dumped into a
grub shell without it ever attempting to download grub.cfg over the
network.
Oops, wrong status. This issue is certainly valid, won't fix is a more
accurate status for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880387
Title:
Security risks: Creates user ubuntu with
You're correct and this pattern can be found in all such templates.
At the time it made sense as the only way to interact with a freshly
created container was through lxc-console which requires a password.
It's one of the many security reasons why we moved from lxc-templates to
distrobuilder and
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668049
Title:
lxd cannot shutdown container
To manage notifications about this bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734410
Title:
Is this still an issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668049
Title:
lxd cannot shutdown container
To manage notifications about this bug go to:
** No longer affects: apparmor (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645037
Title:
apparmor_parser hangs indefinitely when called by
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634199
Title:
In 16.10, LXD won't work with enforced dsnmasq profile
To manage
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_id128_randomize() >= 0'
I believe work in snapd was done to improve seeding so that this
wouldn't be such an issue anymore.
Has this been done and are the cloud images making use of it now?
If so, this can probably be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Pinged in #ubuntu-kernel today for an update. It'd be good to have
groovy signed soon so we can then roll this out to focal users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make
** Changed in: snap-confine (Ubuntu Xenial)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618683
Title:
pivot_root or mounts setup breaks unshare of
** Changed in: snap-confine (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607796
Title:
snap-confine regression when running commands
** 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
Bugs, which is subscribed to Ubuntu.
** Changed in: layer-snap
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709536
Title:
snapd 2.26.14 on ubuntu-core won't start in containers anymore
To manage
Right, I've sent a tweak to LXD upstream to detect such kernel setup and
fallback to xtables, but that's obviously not a situation we'd like to
rely on.
nftables is the current supported way of doing firewalling and is what
Ubuntu uses by default (through shim packages) as of 20.04, so we need
to
Re-opening as I'm not seeing any mention of this being signed now.
** Changed in: linux-kvm (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809
To confirm that this isn't shiftfs related and that we were just causing
the issue to be hidden, I've run the same test on OpenSuse tumbleweed.
I chose that distro because it's apparmor-enabled, has snapd and a 5.4
kernel.
```
localhost:~ # snap install docker
docker 18.09.9 from Canonical*
/var/log/audit.log on Suse logs the same:
type=AVC msg=audit(1590086639.489:8595): apparmor="DENIED"
operation="open" profile="snap.docker.dockerd" name="/entrypoint.sh"
pid=5656 comm="entrypoint.sh" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
--
You received this bug notification
Can you show `snap changes`?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877382
Title:
package lxd 3.0.3-0ubuntu1~18.04.1 failed to
@Khaled yes, it is and we have it now. What's still needed is for the
kernel to be signed so it can be used under secureboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make
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
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
Is that within a privileged LXD container?
If so, that's unfortunately a known snapd issue where the first snap you
install in such a container will fail with that udev error, re-trying
will succeed.
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug
Thanks for your analysis, I've re-targeted to snapd as that's not
expected behavior from it.
** Package changed: lxd (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874878
Ok, fixed the bug tasks and re-opened the bug as we still need this
kernel to get signed.
** Changed in: linux-kvm (Ubuntu)
Status: Fix Released => Triaged
** Changed in: cloud-images
Assignee: Roufique Hossain (roufique) => (unassigned)
** Changed in: linux-kvm (Ubuntu)
Hmm, actually, CONFIG_EFI_STUB is the one we were missing and I'm not
seeing that in your VM either, which makes me wonder how it was booted
in the first place :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Louis, so our testing may in fact have been accurate and things
regressed afterwards :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make linux-kvm bootable in LXD VMs
To
Just tested it now, confirmed that this still boots fine and that this
time the LXD agent successfully starts too.
So this config seems suitable for us. That + enabling kernel signing
will get us working images.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
The `disk-kvm.img` images which are to be preferred when run under
- virtualization, completely fail to boot under UEFI.
+ virtualization, currently completely fail to boot under UEFI.
- This is a critical issue as those are the images that LXD is now pulling
- by
Marking cloud-images side of this as Invalid since the images themselves are
built correctly.
Re-packing with an updated kernel boots just fine, so we only need to track
this against linux-kvm.
** Changed in: cloud-images
Status: New => Invalid
** Summary changed:
- disk-kvm.img aren't
I've tested a kernel with CONFIG_EFI_STUB added (thanks cking!).
This does boot with secureboot enabled, though the LXD agent fails to
start due to lack of vsock.
So in addition to CONFIG_EFI_STUB, it looks like we also need:
- CONFIG_VSOCKETS
- CONFIG_VIRTIO_VSOCKETS
-
Ok, so the fact that we thought this worked is clearly the result from
bad testing on our part, probably because of our simplestreams parsing
code we fixed yesterday...
We obviously still need to move LXD onto this images as booting the non-
kvm images takes twice as long as it should (due to
** Summary changed:
- remove ubuntu-support-status as its a confusing mess
+ [FFe] remove ubuntu-support-status as its a confusing mess
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873362
Title:
Sounds fine, will this be covered in the release notes with a pointer to
whatever replaces it?
I've seen many users use/rely on this tool, so silently dropping it will
be confusing and should be covered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That behavior was last confirmed on Ubuntu 18.04 with nftables 0.8.2-1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872098
Title:
Installing nftables empties the current ruleset
To manage
Public bug reported:
The LXD snap has its own logic to directly add rules to nftables and so
doesn't need "nftables" installed on the system.
The problem is that if one is to install the package, the entire ruleset
gets flushed at that point in time, breaking all LXD instances until LXD
is
https://github.com/lxc/lxd/pull/7167
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
To manage notifications about
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
Bugs, which is
https://github.com/canonical/raft/pull/123
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
To manage notifications
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
Bugs, which is subscribed to Ubuntu.
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
Reproducer on arm64 at least:
```
root@c2400:~# lxc launch images:ubuntu/bionic test-snapd --vm -c
security.secureboot=false -c limits.memory=16GB -c limits.cpu=5-12
Creating test-snapd
Starting test-snapd
root@c2400:~# lxc exec test-snapd bash
root@test-snapd:~# sed
Public bug reported:
This bug leads to data loss and corrupted filesystems!
Over the past few months/years, we've had occasional reports that users see
their systems stuck on a 10min "stopping LXD snap" type message from systemd.
We always thought it was our fault so added a lot of fallback
```
root@buildd08:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
root@buildd08:~# dpkg -l | grep snapd
ii snapd 2.42.1+18.04
arm64
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870539
Title:
package liblxc-common
https://github.com/gTile/gTile/issues/124
** Bug watch added: github.com/gTile/gTile/issues #124
https://github.com/gTile/gTile/issues/124
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870354
Tracked it down to gTile being the issue actually, disabling that one
with the rest of them on seems to fix it.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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...
**
Hello Kellen, or anyone else affected,
Accepted lxcfs into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxcfs/3.0.4-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kellen, or anyone else affected,
Accepted lxcfs into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxcfs/3.0.3-0ubuntu1~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869661
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
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
Bugs, which is subscribed to Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659590
Title:
containers won't start after lxc and apparmor upgrades in trusty
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover and enable
To
** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do lxc-checkpoint again
To manage notifications about
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
anyone still affected by this?
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659590
Title:
containers won't start after lxc and
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
Bugs, which is subscribed to Ubuntu.
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861880
Title:
lxc-attach command does not return error exit code if the command is
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858799
Title:
lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
To manage
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866124
Title:
ps -eo lxc no longer shows a task's lxc container
To manage notifications
Based on autopkgtest history, this must have gotten fixed somehow.
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787436
Title:
lxc
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776381
Title:
lxc-test-api-reboot
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
Bugs, which is subscribed to Ubuntu.
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840639
Title:
Version 3.0.3 breaks
@brauner any idea what that's about?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857046
Title:
lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3
To manage notifications about this bug go
lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837537
Title:
FTBFS since lxc has different version numbers in Debian and
*** 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
Bugs,
** No longer affects: lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508744
Title:
Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade
To manage notifications about this
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700500
Title:
lxc-net
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750654
Title:
"lxc-create -B best" fails on non-btrfs/zfs system
To manage
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713726
Title:
lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8
To manage
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758168
Title:
[16.04] checkconfig: Warning: new{u,g}idmap is not setuid-root
To manage
Our pre-generated oracle images are tested daily and seem to be working
fine.
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757229
We only package LTS releases in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776214
Title:
please package lxc 2.1.1 for xenial
Error was visible in the log, address/port already in use.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715537
Title:
package lxc1
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625235
Title:
lxc doesn't
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699903
Title:
lxc-sshd won't start with 2.0.8
To manage notifications about this bug
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673687
Title:
lx-ls crashes and dumps core
To manage notifications about this bug go
We don't use those template scripts anymore and foreign architecture was
never really supported in the first place (and indeed inconsistently
between templates).
** Changed in: lxc (Ubuntu)
Status: New => Won't Fix
--
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699919
Title:
lxc copy between hosts preserves original uid/gid
To manage notifications
** Changed in: lxc (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594751
Title:
lxc-ls doesn't show nested containers when using an alternate lxc
path
report matches a setup for 16.04 with upstart instead of systemd and no
cgroup-lite or similar pre-mounting the right cgroup, error is correct,
host setup is likely the issue.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Is that still a thing on 3.x or higher?
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614232
Title:
python-lxc attach_wait prevents
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619238
Title:
#cloud-config in user.user-data not running without ip
To manage
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532069
Title:
Can't create a container with a loop backing store in 1.0.8
To manage
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620774
Title:
lxc container does not start: cgroupfs failed to detect cgroup
metadata
To
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302053
Title:
lxc-start with bad container name gives strange err message
To
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556931
Title:
lxc: adt testing failing across the board on ppc64el
To manage
So options here are to apparmor block it, assuming that no common piece
of software relies on it or to mask it with lxcfs (though that still
allows access to user, so not necessarily ideal).
I'm a bit confused as to why this data is accessible to unprivileged
users in the first place, wouldn't
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674679
Title:
lxc autopkgtest fails if http_proxy not set
To manage
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751780
Title:
lxc-snapshot crashes when removing non-existing snapshot
To
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713674
Title:
Starting Xenial lxc without cap_sysadmin fails
To manage
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684481
Title:
KVM guest execution start apparmor blocks on /dev/ptmx now
201 - 300 of 7691 matches
Mail list logo
