Marking the LXC task as Invalid since there's nothing inherently wrong
in 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/1551150
Title:
devel-proposed - android lxc
Basically it looks like that "something" doesn't like the cgroups being
mounted on the phone. Immediately after udev starts, every process gets
a SIGKILL and the phone goes down.
We do need the cgroups filesystems to be mounted for LXC to be happy
though, but we don't need them visible after that
** Attachment added: "lxc-android-config.conf"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551150/+attachment/4680725/+files/lxc-android-config.conf
** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
So it's really unclear to me what's the actual problem, but I got a fix
for the situation that I've tested on a mako here.
--
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/1551150
root@trusty:~# dpkg -L lxc-templates
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/lxc-templates
/usr/share/doc/lxc-templates/copyright
/usr/share/lxc
/usr/share/lxc/templates
/usr/share/lxc/templates/lxc-fedora
/usr/share/lxc/templates/lxc-plamo
/usr/share/lxc/templates/lxc-ubuntu
My guess is that you lxc-templates is from LXC 1.1 while the rest is LXC
2.0.
Partial upgrades aren't supported.
--
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/1590547
Title:
Could it be that you somehow don't have the lxc-templates package
installed?
--
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/1590547
Title:
LXC package for trusty no longer
Can this somehow be reproduced in a VM?
I don't have hardware (nor want any) and debugging over the bug tracker
doesn't seem to be working very well :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
As far as I know, it's impossible to hit this code path on wily, but we
will push the fix as part of 1.1.6 there anyway.
As far as vivid, it's end of life so we won't be doing a SRU there, but
you're welcome to take care of it.
--
You received this bug notification because you are a member of
This was already fixed upstream:
https://github.com/lxc/lxc/commit/23820d548dcd876bd4a8416f80a4d5d1253cd7dd
Vivid is end of life, so if you want a fix for the phone, you could
cherry-pick this into the overlay PPA.
Alternatively we do intend on putting out a 1.1.6 release before 1.1.x
goes
We'd need a reproducer.
** 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/1522992
Title:
/usr/bin/lxc-
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
** Changed in: lxd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: lxd (Ubuntu)
Status: New => Triaged
** Changed in: lxd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I've been running this in production over the past few days without
seeing any problem (running a bit under 12000 containers).
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Uploaded to the 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/1582887
Title:
SRU of LXC 2.0.1 (upstream bugfix release)
Status in lxc package in Ubuntu:
Fix
sion everywhere.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: lxc (Ubuntu Trusty)
Importance: Undecided
Assignee: Stéphane Graber (stgraber)
Status: Triaged
** Affects: lxc (Ubuntu Xenial)
Importance: Undecided
Assignee: Stép
Anders, the LXD equivalent is setting the raw.lxc key to
"lxc.aa_profile=unconfined".
--
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/1575757
Title:
Can't install
Moving over to systemd, our unit is very clear about the expected owner
for the socket. The needed group is created in preinst so is guaranteed
to be there by the time systemd is poked in postinst. LXD itself doesn't
change socket ownership when socket activated and if it did, it would
honor the
I closed the lxd task as our current behavior wrt capabilities is
correct. But I also subscribed the ubuntu-lxc team to this bug so we can
keep an eye on it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
LXC doesn't drop many capabilities, we only really drop mac_admin,
mac_override, sys_time, sys_module and sys_rawio.
That's because we do run workloads which do need the other capabilities,
including cap_sys_admin.
Now in an unprivileged container, having those capabilities will only do you
"apt-get -t trusty-backports install lxd" would have been significantly
easier and less error prone.
But yes, the apt bug itself hasn't been fixed as can be seen by this bug
still being open.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
We'd have to find a way to reproduce it and find what's actually causing
it before we have any chance of fixing it.
--
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/1555760
** Changed in: cgroup-lite (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1570065
Title:
Package cgroup-lite:
I believe someone is fixing the seeds so that it can at least be
uninstalled.
The choice of package selection for a given product isn't up to the
individual packagers so no point in keeping this particular bug open.
There is already an open bug report discussing the choice of packages in
the
That's what unprivileged containers are for.
** 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/1569462
Title:
Not seeing anything wrong with the files above, no subnet conflict or
other network error.
--
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/1569064
Title:
systemctl wants
Ok, the fact that this only happens when it does have an IP may point at
some kind of conflict.
Any chance you can (obviously before reboot), also post "ip addr show",
"ip route show" and the content of /etc/network/interfaces and any file
under /etc/network/interfaces.d/ ?
--
You received this
Can you attach your /etc/default/lxd-bridge and "sudo systemctl status
lxd-bridge"?
Just confirming that everything looks sane on that front.
It does look like systemd triggers on the interface and expects ifupdown
to configure it, waiting forever for it to do so, despite the
possibility that
That redhat bug shows a similar end result though I doubt the cause is
the same in Ubuntu's case. We wouldn't see such random occurrences of
the bug if it was something as simple as a package shipping a completely
broken binfmt snippet.
--
You received this bug notification because you are a
Just found this report too
https://bugzilla.redhat.com/show_bug.cgi?id=986339
** Bug watch added: Red Hat Bugzilla #986339
https://bugzilla.redhat.com/show_bug.cgi?id=986339
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Well, the report was initially reporting an ABI break, my python3
example was to show that it wasn't :)
Anyway, just pushed a no-change rebuild of python-lxc to Xenial now.
Looking at the changelog, the previous rebuild indeed happened right
after 1.1.0 which is when we had the accidental ABI
Okay, lets do this then. FFe granted. Given how critical NM is, I expect
you to be taking a very very close look at any bug reports and IRC
chatter following this change and very quickly upload fixes as needed
until release time so the final delta between what we ship at release
time and final 1.2
** Changed in: vim (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1566579
Title:
FFe: merge with the current Debian package
Okay, the upstream changelog is kinda hard to parse but after a quick
read, the very vast majority of it are bugfixes, additions are mostly to
do with syntax highlighting rather than the core. Getting this would
also reduce our delta with Debian somewhat and help getting rid of
python2, so lets go
The upstream changelog is:
+ 2454 7.4.964 test 87 doesn't work in a shadow directory
+ 1722 7.4.965 on FreeBSD /dev/fd/ files are special
+ 18882 7.4.966 configure doesn't work with a space in a path
+ 3142 7.4.967 cross compilation on MS-windows doesn't work well
+ 2148 7.4.968
Note that LXD as of yesterday does not depend on lxc anymore and also
does not start the bridge (so no dnsmasq or iptables) until you start
interacting with lxd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in
@cmars
Note that the too many levels of symlink is on the host, not in the container
and is the reason why you needed to do the umount and remount.
In fact, your log file says you did get that error:
lxc 20160331183429.245 ERRORlxc_utils - utils.c:safe_mount:1692
- Too many
Your container appears to have an autodev hook script configured and
that script failed to run.
** Package changed: lxd (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Could be that we somehow fixed a bug where the failure to run the script
wasn't considered fatal before but is now.
Anyway, sounds like the error you were getting makes sense to me so
closing this as invalid (not a bug).
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received
Serge is out today actually, I'll try to take a look.
--
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/1559169
Title:
containers no longer start after upgrade to
Curtis: can you paste a log to confirm it's the same issue as Colin?
It looks like some of the cgroup:mixed logic recently introduced in
cgfsng (to match that of the old cgfs backend) is a bit wrong here and
attempts to create a cpu/cpuset,cpuacct symlink instead of symlinking
cpu to
Ok, cool, that confirms it's the same thing.
--
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/1559169
Title:
containers no longer start after upgrade to 2.0.0~rc11-0ubuntu1
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
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/1559169
Title:
containers no longer start after upgrade to
I tried starting stopping trusty, wily and xenial containers, none of
that triggers it.
What's odd though is that every report I've seen so far, show no binfmt
mounted, just the autofs. But LXC itself accesses the path so should
have triggered autofs for the previous container startups.
So
Not having much success reproducing this on a clean machine. In the mean
time, I figured I'd fix my laptop and try to see what changes after a
restart:
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc/
ls: cannot access '/proc/sys/fs/binfmt_misc/': Too many levels of symbolic links
stgraber@dakara:~$ rssh castiana.lan.mtl
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc
ls: cannot open directory '/proc/sys/fs/binfmt_misc': Too many levels of
symbolic links
root@castiana:~# cat /proc/mounts | grep binfmt
systemd-1 /proc/sys/fs/binfmt_misc autofs
The issue isn't inside a container, for that matter lxd is completely
irrelevant here.
We're seeing that weird symlink loop happen randomly on xenial machines.
Normal users likely won't notice it though as they don't use that mountpoint,
LXC users do though as LXC bind-mounts it into the
root@castiana:~# systemctl status proc-sys-fs-binfmt_misc.mount
● proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System
Loaded: loaded (/lib/systemd/system/proc-sys-fs-binfmt_misc.mount; static;
vendor preset: enabled)
Active: inactive (dead) since Sat 2016-03-12
Just tested a dozen Xenial systems I have around and only found the
issue on one, my laptop today:
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc
ls: cannot open directory '/proc/sys/fs/binfmt_misc': Too many levels of
symbolic links
root@castiana:~#
--
You received this bug notification
I'm trying to get a system that doesn't even have lxc installed to get
into the 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/1555760
Title:
Too many levels of
Upstream argument naming appears to be aligned with the namespace name
in /proc, so it's a safe bet that --cgroup will be the final option
name.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Is Network Manager 1.2 out yet? I don't seem to remember seeing an
announcement.
If not, when is it expected to be out?
Also, can you comment on our existing delta (phone & others) and give
some more details on how those will be updated and tested?
Overall, I absolutely support us moving to
That part of the init script looks just plain wrong to me... I'm
guessing the intent was for /dev/cpuctl to be a bind-mount of
/sys/fs/cgroup but that's not at all what the code does.
I'll update my local copy here to replace that by a simple symlink from
/dev/cpuctl to /sys/fs/cgroup/cpu
--
Update init script is: http://paste.ubuntu.com/15264484/
--
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/1551150
Title:
devel-proposed - android lxc container fails to start
I have a debdiff ready to upload for the changes so far but will wait
until we figure out the rest of this issue.
Serge Hallyn is also working on a cgroup-lite changes to get us rid of
most of that diff too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That is very weird, the cgroup-lite upstart job should result in your
case in 4 cgroup mounts, so I'm not sure why it's not happening here...
Could you run "bash -x /bin/cgroups-mount" as root and post its output
including a dump of /proc/self/mountinfo before and after running it?
that should
So far that does seem to confirm the hypothesis that since the phone has
systemd installed (but unused), this meets lxc's dependency on systemd |
cgroup-lite but as upstart is used to boot and upstart itself doesn't
mount the cgroup controllers, this results in a system without cgroups
mounted.
Some more information on cgroup-lite and where it may fail.
- cgroup lite is triggered on "mounted MOUNTPOINT=/sys/fs/cgroup" => the path
is shown as mountend above, so not it
- The job then gets skipped if /bin/cgroups-mount doesn't exist => part of the
cgroup-lite package, so not it
- The
That mountinfo shows no mounted cgroup controller, hinting that cgroup-
lite didn't start or otherwise failed to start.
Could you look for a /var/log/upstart/cgroup-lite.log file?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Do you know if the phone actually uses systemd as its init system
nowadays?
LXC requires either systemd or cgroup-lite to mount all the cgroup bits
properly, if systemd is installed but not used, that could explain what
you are seeing. Installing cgroup-lite should have fixed it though,
unless
We're gonna need a /proc/self/mountinfo output if we want to figure out
what the controller #7 is on your system...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150
Can you paste the content of /proc/mounts on such a system and confirm that
either one of those is true:
- systemd is installed and used as init system
- cgroup-lite is installed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
That's very weird, all my xenial test systems show lxc-container-
default-cgns in the apparmor_status output
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1549363
Title:
As for the cgroups, we've noticed at least one issue in the cgfs logic
of LXC which was fixed earlier today, the package is still going through
QA (currently in proposed), should make it to the release pocket within
a couple of hours.
The fix was specifically to fix unprivileged but root-owned
Hmm, does /etc/init.d/apparmor reload fix the profile not being loaded?
We've not been introducing new profiles very often and those profiles
are loaded through apparmor includes so I can certainly see a standard
dh_apparmor being confused by it and not reloading everything properly
on upgrade.
)
Status: New => Won't Fix
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: juju-core (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Not much we can do about the IP address though. For the MAC it's
unlikely that anything in the container is tied to it so we can just
generate a fresh one without requiring any knowledge about the workload
or the environment.
An IP address is much more problematic because maybe you did mean to
** No longer affects: lxd (Ubuntu)
--
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/1544157
Title:
lxc exec not working in xenial
Status in lxc package in Ubuntu:
Fix
** Project changed: lxc => lxc (Ubuntu)
--
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/1428490
Title:
AppArmor vs unix socket inside LXC containers
Status in lxc package in
** Project changed: lxc => lxc (Ubuntu)
--
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/1359224
Title:
Feature request: Add support for multiple bridges
Status in lxc package
** Project changed: lxc => lxc (Ubuntu)
--
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/1302053
Title:
lxc-start with bad container name gives strange err message
Status in
** Project changed: lxc => lxc (Ubuntu)
--
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/1436722
Title:
lxc domain setup instructions are incorrect
Status in lxc package in
** Project changed: lxc => lxc (Ubuntu)
--
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/1470599
Title:
Stuck mountall inside container
Status in lxc package in Ubuntu:
New
** Project changed: lxc => lxc (Ubuntu)
--
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/1441307
Title:
lxc-clone makes new copies of each hardlinked file
Status in lxc
** Project changed: lxc => lxc (Ubuntu)
--
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/1472929
Title:
undefined symbol: cgmanager_get_pid_cgroup_abs_sync
Status in lxc
** No longer affects: 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/1342960
Title:
comments in common.conf must be updated
Status in lxc package in Ubuntu:
Fix
** Project changed: lxc => lxc (Ubuntu)
--
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/1486073
Title:
'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7
** Project changed: lxc => lxc (Ubuntu)
--
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/1445539
Title:
Can't create vivid lxc on trusty
Status in lxc package in Ubuntu:
** Project changed: lxc => lxc (Ubuntu)
--
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/1521151
Title:
init: lxc-instance main process terminated with status 255
Status in
** No longer affects: 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/1285850
Title:
interuppting lxc-clone can destroy source container
Status in lxc package in Ubuntu:
** Project changed: lxc => lxc (Ubuntu)
--
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/1532069
Title:
Can't create a container with a loop backing store in 1.0.8
Status in
Oh, did I mess up the upstream fix too then?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1545884
Title:
Xenial's shadow regresses subid allocation logic (wastes uids
root@dakara:~# useradd --system blah
root@dakaracat /etc/subgid
lxd:10:65536
root:10:65536
sshd:165536:65536
sbuild:231072:65536
blah:296608:65536
blah most definitely shouldn't be there!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
That's on current Xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1546232
Title:
Applet doesn't update after adding a VPN
Status in network-manager
Public bug reported:
I just added a VPN and it doesn't show up in the list, had to restart
network-manager for it to show up...
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: lxd (Ubuntu)
Status: Triaged => Fix Committed
** Package changed: lxd (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1537939
Public bug reported:
Back in trusty I wrote a patch to shadow which makes sure we only ever
allocate a 65k uid/gid map to new users that aren't a system user (no
--system flag and not a system uid/gid).
This has regressed recently in Xenial and on a fresh install I found
myself with about 15
** Package changed: lxc (Ubuntu) => lxd (Ubuntu)
--
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/1544157
Title:
lxc exec not working in xenial
Status in lxd package in
Up until last week, cloud images were being built just fine with lxc and
lxd in them, starting this week, they fail, that seems like a regression
to me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
I'm marking the lxc task invalid as no packaging change occurred on
lxc's side and this, admittedly rare, init script configuration has been
supported for years and should still be supported.
Directly subscribing the containers team though so we can help track
down the source of the regression.
I just compared the content of lxc 1.1.5-0ubuntu6 which I'm assuming was
the last working LXC version in cloud images and lxc
2.0.0~beta2-0ubuntu2 that we have now and neither provides any
/etc/init.d script nor am I seeing any packaging change on our side
which would explain this.
Packaging diff
Subscribing Martin Pitt who very recently merged init-system-helpers.
I've not yet read the diff, but this seems like a fair bet as to what
changed recently (last upload was Feb 5).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Under upstart, I can have the following line in my /etc/fstab:
tmpfs /run tmpfs defaults,size=10M 0 0
At mount time, mountall will use /etc/fstab as an override for the
internal fstab (/lib/init/fstab) and so I end up with /run mounted with
a 10MB limit.
Under systemd,
Hello Ryan, or anyone else affected,
Accepted network-manager into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/0.9.8.8-0ubuntu7.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** No longer affects: lxd (Ubuntu)
--
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/1527374
Title:
privilege escalation on attach through ptrace
Status in linux package in
Sounds like a lxcfs or cgmanager issue, moving to lxcfs for now.
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1527666
So unless ifup/ifdown brings the aliases up/down itself, I don't think
filtering those out is the right fix.
Take this scenario as an example:
- System boots quickly
- networking.conf kicks in, fails to bring eth0 because it's not showed up yet
(happen reasonably often with complex blade
Also note that I'm removing the lxd task as this does appear to be a
systemd issue, ~ubuntu-lxc will remain subscribed to the issue though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
As a reminder:
- http://lists.freedesktop.org/archives/systemd-devel/2015-January/027246.html
- http://lists.freedesktop.org/archives/systemd-devel/2015-January/027323.html
http://cgit.freedesktop.org/systemd/systemd/commit/?id=874d3404cbf2363604106c8f86683db4082691ea
The code change at that
Moving this one over to LXC, a quick look at the code (thanks Serge)
seems to indicate that we only support personalities with seccomp for
x86 and power. A similar code path must be added for arm on aarch64.
** Changed in: lxd (Ubuntu)
Status: New => Triaged
** Changed in: lxd (Ubuntu)
401 - 500 of 758 matches
Mail list logo
