@shemgp, this suggests that you're using a non-ubuntu kernel which comes
with incomplete apparmor support. This typically happens when you're
using a mainline kernel build rather than an official Ubuntu kernel.
You can force LXD to use such a kernel, though as mentioned, confinement
will be partia
Avahi is setting some rather strict rlimits which affect everything
which uses that kernel uid, crossing container boundaries and so
breaking containers.
Unfortunately MAAS requires a privileged container right now, so you
can't resort to uid mapping to avoid this problem. At the LXD level, all
we
(but keeping ~ubuntu-lxc subscribed to this bug)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869
Title:
maas install fails inside of a 16.04 lxd container due to avah
It's not realistic to do this:
- lxc-create is only called when the container is created whereas
lxc.network.* can be changed at any point in time
- The Ubuntu template maintains a cache of the generated system, so we'd need
to do these as an extra step when re-using the cache as we sure wouldn
** Changed in: lxc (Ubuntu)
Status: New => 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/1661825
Title:
interfaces always dhcp in ubuntu template
Status in
Oops, bad copy/paste in the first comment, LXCFS has only had 6 previous
point 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/1660844
Title:
SRU of LXC 2.0.7 (upstre
Additionally, this package is in Zesty already and has been
automatically pushed to thousands of users of the upstream LXC stable
PPA and we monitor new bug reports for 2.0.7 very closely.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
We have autopkgtest coverage for this, combined with manual testing of
it prior to release and we also look very closely at bug reports we get
upstream from users of distributions which are already shipping this
release.
Same thing we've been doing for the past 8 point releases, so far with
all is
version everywhere.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: lxc (Ubuntu Trusty)
Importance: Medium
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxc (Ubuntu Xenial)
Importance: Medium
Assign
Marking the LXD side of this as Invalid since there's unfortunately
nothing we can really do about this.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ub
Removing the LXD task, this is yet another apparmor bug from the
apparmor stacking/namespacing change which was backported to Xenial.
Basically, dhclient is now being confined by apparmor inside the
container, unfortunately, apparmor doesn't behave in the exact same way
when it's interpreting a pr
** Changed in: lxc (Ubuntu Precise)
Status: In Progress => 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/1647016
Title:
SRU of LXC 1.0.9 (upstream bugfix
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
Looks like this version passes all our tests just fine and we haven't
heard anything bad from users of -proposed or other distros that are
already including 1.0.9.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member
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
Unfortunately the kernel overmounting security check won't let you do
so.
This security check is there in the event that /home/blah contains some
files which the /home/blah mount hides. Now allowing an unprivileged
user to bind-mount /home without /home/blah on top of it would un-hide
those files,
That's perfectly normal, if a bit confusing.
lxc-tests only exists in precise-backports while liblxc1 exists in both
the release pocket and the backports pocket.
Apt policy is to never automatically pull from backports unless the
package only exists there.
As a result, apt will pull lxc-tests f
You should be able to use "systemctl edit" to set PrivateNetwork=no as a
temporary workaround.
--
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/1656024
Title:
Units using Pr
Looks like the problem is to do with systemd and it failing to spawn
units that have:
PrivateNetwork=yes
I'm not sure exactly what systemd attempts to do which doesn't work in
an unprivileged container, but the answer is almost certainly to have it
not do that :)
Re-assigning bug to systemd.
**
Nope, task removed.
** No longer affects: lxc (Ubuntu)
** No longer affects: lxc (Ubuntu Wily)
--
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/1542049
Title:
lxc: ADT exercis
Public bug reported:
The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
regression in cups-browsed (shipped by cups) which now fails to start
and gets respawned in a loop by systemd until it completely gives up.
To reproduce:
- lxc launch ubuntu:16.04 xen
- lxc exec xen -- ap
This was fixed upstream and included in our stable branch. A cherry-pick
was uploaded to Zesty and all tests were run successfully against it.
I have now uploaded the same thing for xenial and yakkety, they are in
the queue waiting for a SRU team member to approve them.
Once the Xenial SRU is thr
igned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Yakkety)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** No longer affects: lxc-android-config (Ubuntu Xenial)
** No longer affects: lxc-android-config (Ubuntu Yakkety)
** No longer affects: lxc-android-config (U
Thanks. I think the problem is a newly introduced check for path
writeability which is harmless and in fact, potentially useful in just
about all cases but the weird Ubuntu Phone case where / is read-only,
confusing that check.
@Christian: Can you look into fixing this? I suspect we only really ca
stgraber@dakara:~$ lxc launch ubuntu:16.04 nfs -c security.privileged=true -c
raw.lxc=lxc.aa_profile=unconfined
Creating nfs
Starting nfs
stgraber@dakara:~$ lxc exec nfs bash
root@nfs:~# apt install nfs-kernel-server
Reading package lists... Done
Building dependency tree
Reading state information.
@Justin: The second entry isn't ignored, it will be used when the
container starts. Though as Christian said, you do need to restart the
container for this to apply.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubunt
What are the permissions on /var/lib/lxc on such devices?
--
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/1653725
Title:
lxc-android-config not starting on ubuntu-touch/staging
** Changed in: lxc (Ubuntu Trusty)
Status: In Progress => 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/1647010
Title:
SRU of LXC 2.0.6 (upstream bugfix r
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
Been running this for a week without a problem. Autopkgtest is a bit confused
due to a mixup with the old go-lxc, but LXC's own tests pass and the test
results against the new go-lxc are good too.
Releasing.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received
Autopkgtest found a regression related to unprivileged container
execution when combined with overlayfs and the trusty kernel (3.13).
Marking this as verification-failed and will be tracking this done,
fixing upstream and cherry-picking a fix (once we know exactly what's
going on).
This failure
Public bug reported:
Since the last Network Manager upload my systems get a completely empty
/etc/resolv.conf when they'd before have a directly managed file by
NetworkManager.
I have dns=default set in NetworkManager.conf which tells NetworkManager
to directly manage that file. But that's now ap
s well, making sure we have the same version everywhere.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: lxc (Ubuntu Precise)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: In Progress
** Affects: lxc (Ubuntu Trusty)
ecided
Status: Fix Released
** Affects: lxc (Ubuntu Trusty)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: In Progress
** Affects: lxc (Ubuntu Xenial)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: In Progress
** A
** Changed in: lxc (Ubuntu Trusty)
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/1632144
Title:
SRU of LXC 2.0.5 (upstream bugfix relea
Did you install squashfuse in your container?
--
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/1611078
Title:
Support snaps inside of lxd containers
Status in Snappy:
Fi
This has been confirmed to affect both the 4.4 and 4.8 kernels.
** Project changed: apparmor => apparmor (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: lin
Christian will be testing 4.4.0-45 to see if we hit this issue with a
pre-aastacking kernel.
--
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
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1639345
Title:
lxc-attach to malicious container allows acces
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags added: bot-stop-nagging
--
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/1639345
Title:
lxc-attach to mal
Getting openpty called in the container would solve a lot of problems
for us but it's not possible to do in a safe way as it'd effectively
rely on the container's filesystem which the container user can change
or fake at will, allowing for attacks on the host's C library and LXD
itself.
** Also af
The reason why your upgrade broke is because you were using the LXC PPA
on 14.04 which effectively meant you had a more recent version of LXC
than is in 16.04.
You should be able to fix things by either removing all those packages
and reinstalling them clean from the 16.04 archive, or by re-enabli
As for Launchpad, bug reports are tied to source package name, instead
of binary package name, so the "lxc" package is correct.
--
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/163
** Package changed: linux (Ubuntu) => lxc (Ubuntu)
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Changed in: lxc (Ubuntu Zesty)
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/1635639
Title:
Seccomp error with 2.0.5-0ubuntu1
root@castiana:~# zfs set quota=2EB encrypted/lxd/containers/zesty
root@castiana:~# echo $?
0
root@castiana:~# zfs get quota encrypted/lxd/containers/zesty
NAMEPROPERTY VALUE SOURCE
encrypted/lxd/containers/zesty quota 2E local
So as can be seen, ZFS allows s
** Changed in: lxc (Ubuntu Zesty)
Status: Triaged => 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/1635639
Title:
Seccomp error with 2.0.5-0ubuntu1~ubun
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
Confirmed on both xenial and yakkety.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1635639
Title:
Secc
That's actually completely expected since you didn't set the "name"
property on that network device.
"eth0" above refers to the LXD device entry name which has nothing to do
with the device name in the container.
So you need to do:
lxc profile device add devstack-profile eth0 nic nictype=bridged
** Changed in: lxc (Ubuntu)
Status: In Progress => Triaged
** Also affects: lxc (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Zesty)
Importance: High
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Also affects:
I fixed this in upstream LXC yesterday, will upload SRUs today.
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu)
Status: New => In Progress
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You rece
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
Been running this for a week now, haven't run into problems.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs
Yes, so basically we have:
- dnsmasq.pid (create + read/write by dnsmasq)
- dnsmasq.raw (read by dnsmasq)
- dnsmasq.hosts (read by dnsmasq)
- dnsmasq.leases (create + read/write by dnsmasq)
I'd be tempted to just go with:
/var/lib/lxd/networks/*/dnsmasq.pid rw,
/var/lib/lxd/networks/*/dnsmasq
/var/lib/lxd/networks/*/dnsmasq.leases rw,
should work fine
--
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 dsnmasq
The interface name is decided by the user in LXD 2.3 or higher, so it
can be any valid interface name.
--
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
So I'm not convinced that doing this in dhclient is necessarily right.
Unlike IPv4 where DHCP operates over a raw socket, in IPv6 mode,
dhclient is just a regular network client and as such requires a source
address to be set so it can contact the network (the link-local address
in this case).
As
So I suspect the reason for this behavior is that there is no reason why
you'd want to run dhclient in IPv6 mode before you've brought up the
interface and parsed the router advertisement.
That's because unlike IPv4, IPv6 configuration is mostly done through
router advertisements which happen enti
** Changed in: lxd (Ubuntu Xenial)
Status: New => Fix Committed
--
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/1611078
Title:
Support snaps inside of lxd container
So it's expected that the download template images will not replicate
any host settings (locales, timezone, ...) as those are completely self-
contained images.
As discussed on IRC, it looks like Xenial needs you to also change the
/etc/localtime symlink, which is why your manual change worked for
lxc (Ubuntu Trusty)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxc (Ubuntu Xenial)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: In Progress
** Changed in: lxc (Ubuntu)
Status: New =>
** Changed in: lxc (Ubuntu Trusty)
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/1615099
Title:
SRU of LXC 2.0.4 (upstream bugfix relea
Marking this bug fix released as all the bits we wanted done here have
been done.
We still have a separate bug open for the dependency on squashfuse and
its SRU to xenial.
** Changed in: snappy
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Closing as 1.1.2 has long been out of support and we've not heard of
anything like that on more recent Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: lxc (Ubuntu)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a
Re-opening LXC task as it wasn't fixed, the fix was reverted as it was
causing an FTBFS.
** Changed in: lxc (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https:
** Changed in: lxd (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: lxd
--
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/1611078
Title:
Support
Hello Tyler, or anyone else affected,
Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
You can check for "lxd-*" or "lxc-*", that should catch anything we do
with LXC or LXD.
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
htt
Public bug reported:
Now that we have support for apparmor namespacing and stacking,
unprivileged containers can and should be allowed to load apparmor
profiles.
The following changes are needed at least:
- Change the systemd unit to remove the "!container" condition
- Change the apparmor init
Since you're using LXC on Debian and not on Ubuntu, can you file a bug
at https://github.com/lxc/lxc instead?
** 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 Ub
LXC isn't running by default, it isn't even installed by default.
LXD is installed by default in server and cloud images as was decided by the
product manager for those.
The only resources LXD uses is disk space as it's socket activated and
will not actually run until you talk to it (so no CPU or
What init system are you using on this system?
systemd would automatically mount those cgroups which then wouldn't need
the help of cgroup-lite (preferred) or cgroupfs-mount (which you used).
But if you're using upstart on Ubuntu 16.04, then you indeed do need one
of those two packages installed.
How far back is this supported? LXC is automatically backported all the
way back to trusty without any change to the packaging being required
right now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bu
There is a LXD property which should have it update the relevant files
for you.
lxc config set user.network_mode link-local
Setting that prior to the first container startup should fix your
problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
cloud-init in LXD triggers after network is up, so indeed, in your case
it won't run.
Your problem is that you have the network defined as DHCP so this will
hang your boot and cloud-init. If you had /etc/network/interfaces (or
the new cloud-init network-data stuff) marked as "manual", then the
net
** Changed in: lxd (Ubuntu)
Status: Triaged => 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/1577001
Title:
Installing lxd leaves /var/lib/lxd/unix.soc
I had production servers running this for the past week, all good.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.ne
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
Update package uploaded to yakkety and xenial-proposed, should be
accepted shortly.
--
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/1615099
Title:
SRU of LXC 2.0.4 (upstream bu
Fix is going through testing upstream
https://github.com/lxc/lxc/pull/1152
--
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/1615099
Title:
SRU of LXC 2.0.4 (upstream bugfix rele
We had a report of checkpoint/restore failure on LXC 2.0.4 upstream,
marking this as vertification-failed for now. I will recycle this bug as
soon as we have an upstream fix for it later today.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notif
This is a kernel bug which sforshee has been working on. It should be
included in the next round of kernel updates.
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification becau
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxc (Ubuntu Xenial)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
** Also affects: lxc (Ubuntu Trusty)
So I just ran into the exact same problem with my personal VPN when I do
have both IPv4 and IPv6 configured to route all traffic over the VPN.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
** Changed in: lxd (Ubuntu)
Importance: High => Low
--
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/1577001
Title:
Installing lxd leaves /var/lib/lxd/unix.socket with wr
** Changed in: lxd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: bind9 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Bug watch added: LXD bug tracker #1942
https://github.com/lxc/lxd/issues/1942
** Also affects: lxd via
https://github.com/lxc/lxd/issues/1942
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
** Changed in: lxd (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: snappy
Status: New => Fix Committed
** Changed in: snappy
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a
** Changed in: lxd (Ubuntu)
Status: New => In Progress
** Changed in: lxd (Ubuntu)
Importance: Undecided => Critical
** Changed in: lxd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
We can't merge it before then as there's currently no way for us to
detect a broken kernel vs a good kernel, so merging this work would
effectively break all LXD users on a kernel that pretends to support
namespacing and stacking, such as the 16.04 release kernel.
--
You received this bug notific
Yeah, LXD will need updating but we're already tracking this work and
actually have it all ready to merge as soon as your team delivers a
working kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
http
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Critical
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team
You will also need to upgrade to the 4.4 kernel (linux-generic-lts-
xenial) if you want containers to actually work as prior kernels for
power8 didn't properly support seccomp.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to l
Moving this one over to the lxc package.
https://github.com/lxc/lxc/issues/1046 upstream.
** Package changed: lxd (Ubuntu) => lxc (Ubuntu)
** Bug watch added: github.com/lxc/lxc/issues #1046
https://github.com/lxc/lxc/issues/1046
** Changed in: lxc (Ubuntu)
Status: New => Triaged
**
Could you include what gets written to your syslog while the VPN
connection is established?
SIGUSR1 to dnsmasq tells you what server it's talking to, but
unfortunately not for what domain...
Based on your described symptoms, I'm suspecting that the openvpn plugin
told NM to configure dnsmasq only
I've had this running for the past few days on a few servers, no problem
found and we haven't received any negative feedback from yakkety, PPA or
backports users either.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
** Changed in: lxc (Ubuntu Trusty)
Status: New => Fix Released
** Summary changed:
- SRU of LXC 2.0.13(upstream bugfix release)
+ SRU of LXC 2.0.3 (upstream bugfix release)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: lxc (Ubuntu Trusty)
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/1582887
Title:
SRU of LXC 2.0.1 (upstream bugfix relea
Public bug reported:
LXC upstream released LXC 2.0.2 & 2.0.3 as bugfix releases with following
changelog:
- apparmor: Refresh generated file
- apparmor: add make-rslave to usr.bin.lxc-start
- apparmor: Allow bind-mounts and {r}shared/{r}private
- apparmor: allow mount move
- apparmor: Update
301 - 400 of 759 matches
Mail list logo
