And that only fails on s390x?
--
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/1969905
Title:
lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc
Are the tests run with security.nesting=true set?
--
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/1959013
Title:
systemd test_exec_umask_namespace fails in privileged
This was caused by a recent change to how we handle selinux and apparmor config
options when LXC is compiled without support. I've sent
https://github.com/lxc/lxc/pull/3969
specific to stable-4.0.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu Impish)
Status: In Progress => 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/1938771
Title:
lxc-test-rootfs test regression
Also added tests around rootfs mount options.
** Changed in: lxc (Ubuntu Impish)
Status: Confirmed => 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/1938771
Thanks for reporting this. I've fixed this in:
https://github.com/lxc/lxc/pull/3921
** Changed in: lxc (Ubuntu Impish)
Status: New => Confirmed
** Changed in: lxc (Ubuntu Impish)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification b
Hm, what is the LXC version used here? Is it the one in Bionic?
--
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:
lxc-test-api-reboot will hang with autopkgtest
I'm currently treating this as an upstream kernel regression reported
here
https://lore.kernel.org/regressions/20210607142245.eikvyeacqwwu6dn3@wittgenstein
We should wait whether a simple revert will be acceptable or whether
anything else is needed from LXC specifically.
--
You received this
On Mon, Jun 07, 2021 at 05:14:50AM -, Andrea Righi wrote:
> Public bug reported:
>
> The lxc autotest is failing with the following error(s) on the latest
> kernel linux-unstable 5.13:
>
> FAIL: lxc-tests: lxc-test-apparmor (1s)
> ---
> failed - opened /sys/kernel/uevent_helper
> ---
> PASS:
This is with 4.0.4 and the bug is fixed in 4.0.6 which it seems hasn't
made it into Groovy yet (but is released). I'm not sure what Stéphane's
timeline is there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
This has been fixed a long while ago:
commit 920cbb00268ce50d1306daebb74871f66583a46c
Author: Christian Brauner
Date: Mon Nov 18 15:08:22 2019 +0100
tests: use /dev/loop-control instead of /dev/network_latency
BugLink: https://bugs.launchpad.net/bugs/1848587
The latter device
** Changed in: lxc (Ubuntu)
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/1888705
Title:
lxc ftbfs against libselinux 3.1
Status
https://github.com/lxc/lxc/pull/3498
** 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/1888705
Title:
lxc ftbfs
This is a bug we fixed in our stable-3.0 branch and is fixed in the Ubuntu lxc
3.0.4 packages. See
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587
and specifically this commit:
commit 11fc6882f7bfd40fbcda6a3a7f7c1bca50df3f2b
Author: Christian Brauner
Date: Mon Nov 18 15:08:22 2019
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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 test
This is a regression in overlayfs for the 5.8 kernel. The same test
works fine on an earlier kernel with the same lxc version.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I think that's already fixed in the edge snap but we haven't yet rolled
that out to stable. Can you test with edge?
--
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/1869661
No, but might have been an allocation error which we fixed in the meantime. The
error can only come from:
ENOMEM The kernel could not allocate a free page to copy filenames or data into.
That's the only reason mount() can fail with ENOMEM from just glancing at the
manpage. I'll take another
This might be caused by changes to busybox since this looks like it's testing
liblxc-3.0.4. In any case, I believe that the following commit in the
stable-3.0 tree would fix it:
https://github.com/lxc/lxc/commit/3daa49d845b153dfb2012b61dba763cbc6e11374
--
You received this bug notification
On Mon, Dec 09, 2019 at 08:41:18PM -, Ryutaroh Matsumoto wrote:
> https://github.com/lxc/lxc/issues/3221 Another LXC-container-doesn't
> -start-at-all type issue also observed on Ubuntu Eoan with
> systemd.unified_cgroup_hierarchy as well as Fedora 31.
That seems specific to LXC stable-3.0
** 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/1855513
Title:
log file
Status in lxc package in Ubuntu:
Invalid
https://github.com/lxc/lxc/issues/3198#issuecomment-562064091
--
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/1850667
Title:
cgroup v2 is not fully supported yet, proceeding
** Changed in: lxc (Ubuntu)
Status: In Progress => 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/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with
Sorry, mail got lost. Here's a fix:
https://github.com/lxc/lxc/pull/3187
** Changed in: lxc (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Is this a flake or consistently reproducible?
--
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/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
Status
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Invalid
** Changed in: lxc (Ubuntu Bionic)
Status: New => Incomplete
Fix here:
https://github.com/lxc/lxc/pull/3034
** Changed in: lxd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: lxd (Ubuntu Eoan)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: Invalid => In Progress
** Changed in: systemd (Ubuntu
Several people tried to namespace this but this is really tied to a
physical machine so it's kinda tricky to fake.
--
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/1831258
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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/1825155
Title:
lxc-start crashed with SIGSEGV in
Okay, I have a fix for the shiftfs side I think. Attached here.
** Patch added: "UBUNTU: SAUCE: shiftfs: use correct llseek method for"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812/+attachment/5256074/+files/0001-UBUNTU-SAUCE-shiftfs-use-correct-llseek-method-for-d.patch
--
Public bug reported:
Hey everyone,
We recently pushed support for ambient capabilities and namespaces filesystem
capabilities
to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have released a
version 2.26
of libcap2. Note that libcap2 has moved to a new location [2]
The 2.26
If the systemd version doesn't support hybrid cgroup layout on xenial
then fine but I thought it did. But please make sure that Xenial doesn't
have anything mounted on /sys/fs/cgroup/unified.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: iptables (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
If you think that you have found an actual security bug please file it
as a new one to follow best security practices.
--
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/1783591
On Thu, Aug 30, 2018 at 08:02:56PM -, Salvatore Bonaccorso wrote:
> One can still test existence of files with those patches, but I guess
> this was explicitly not part of the fixes?
Is there a reproducer?
Yes, the open() can fail and we will report back to the user that the
open() failed but
New version to apply cleanly to master.
** Patch added:
"0001-CVE-2018-6556-verify-netns-fd-in-lxc-user-nic-master.patch"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/+attachment/5172186/+files/0001-CVE-2018-6556-verify-netns-fd-in-lxc-user-nic-master.patch
--
You received
On Fri, Jul 27, 2018, 21:21 Stéphane Graber
wrote:
> Ok, thanks for the update. I've now updated the bug once again to move
> all the tasks over to the kernel. Can you attach the kernel patch here
> when you can, I'm sure some of the subscribers may want to test this
> ahead of the Ubuntu kernel
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Confirmed
--
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/1575779
Title:
hostnamectl fails under lxd
*** This bug is a duplicate of bug 1780227 ***
https://bugs.launchpad.net/bugs/1780227
This is an AppArmor bug that I reported and which is tracked here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780227
So please close here in favor of that bug.
Christian
** Changed in: lxd
What's your LXC version?
--
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:
Unknown
Status in lxc package in Ubuntu:
So, the good news is that this is all fixed upstream starting with 4.17 with
the socket mediation patchset that got merged a short while ago. The bad news
is that we need to get this patchset backported and it is quite large:
Hey, so we're seeing an instance of this issue and the problem is that a
lock is taken on an fd instead of a path. This should be legal and we
urgently need a fix for this since this is starting to break all systemd
services running in a container that use PrivateUsers= and anything else
that hits
On Thu, Jun 14, 2018 at 04:19:39AM -, Po-Hsu Lin wrote:
> Is there anything that I can do for debugging this?
Hm, you could try manually creating a busybox container and trying to:
- shut it down
- reboot it
with lxc-stop
Christian
--
You received this bug notification because you are a
On Tue, Jun 12, 2018 at 8:39 AM, Po-Hsu Lin wrote:
> If you leave it there for a long period, it will time out in the end:
> make[1]: Leaving directory '/tmp/autopkgtest.ZiY11u/build.Nic/src'
> FAIL: lxc-tests: lxc-test-api-reboot (9845s)
The API reboot tests will hang indefinitely if the
On Tue, Jun 12, 2018 at 12:46 PM, Free Ekanayaka
wrote:
> It might be a duplicate of https://github.com/lxc/lxd/issues/4485 (which
> is fixed in 3.0.1, now in -proposed I believe).
This is a LXC integration test that is failing, not a LXD one. :)
>
> We'd need to see the logs of the LXD daemon
This is indeed pretty important for some use-cases so we should try to
come up with a reasonable solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1755250
Title:
We just had a short discussion on systemd and for systemd 229 on 16.04
we also need:
9e5f825280192be429cc79153235d12778427fae :
https://github.com/systemd/systemd/commit/9e5f825280192be429cc79153235d12778427fae
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Hey,
Currently any service that has PrivateDevices=true set will fail to
start in unprivileged containers since mknod is not possible and in
privileged containers that drop CAP_MKNOD. I pushed a patch to systemd
upstream that solves this problem and makes PrivateDevices
What? That's totally possible. Simply try unshare -n inside an
unprivileged container as root.
--
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/1635382
Title:
** 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/1758380
Title:
unpriveleged containers no longer could start
Can we get some logs for the LXC containers that created and fail?
Otherwise this is very much a black box.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1757470
Title:
Sorry for the brevity before. I tested this with systemd 23{5,6}
inside xenial and artful containers which is really the only case
where it matters.
A systemd with my patch applied would happily:
1. skip over undelegated /sys/fs/cgroup/unified mountpoints
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done-artful
--
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/1734410
Title:
** Changed in: lxc (Ubuntu)
Status: Confirmed => 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/1751780
Title:
lxc-snapshot crashes when removing
** Changed in: lxc (Ubuntu)
Status: New => Won't Fix
** Changed in: lxc (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
On Tue, Feb 20, 2018 at 08:43:41PM -, Martin Pitt wrote:
> Public bug reported:
>
> As per documentation, the `-B best` option should automatically select
> the best backingstore, falling back all the way to dir.
>
> But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
Hm, is
On Thu, Feb 15, 2018 at 11:29:03AM -, Aleksa Sarai wrote:
> I've just sent a request for a CVE. I'm working on the patch now. My
I assume the CVE will at least be correctly attributed to Craig.
Christian
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** No longer affects: autopkgtest (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/1553097
Title:
lxc-attach does not output stderr any more if stdout is redirected
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1567037
Title:
lxc-attach crashed with SIGSEGV in
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Released
** 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/1690125
Title:
hybrid control
Public bug reported:
Hey everyone,
Current systemd versions all fail when the unified cgroup hierarchy is
not-writable. This is especially problematic in containers where the
systemd administrator might decide to not delegate the unified hierarchy
or when running with a liblxc driver that
Public bug reported:
Hi everyone,
systemd-sysctl in systemd versions prior to 232 will exit with FAILED
when not being able to apply kernel variables. In containers it should
simply move on and exit with SUCCESS. Upstream systemd carries
appropriate patches for this already. The relevant commits
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1692111
Title:
Unable to configure raw.id_map with
Has the `/etc/init/` directory and associated files been removed from
artful I remember @xnox removing old init scripts.
--
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/1713726
Hey everyone,
Uust as an fyi: I sent a branch https://github.com/lxc/lxc/pull/1713
which is now merged that makes LXC handle the hybrid cgroup case
provided the cgroup v2 mount does not bind any controllers (Which is the
current default). It will be included in the next LXC release.
Thanks!
On Fri, Jun 23, 2017 at 10:19:46AM -, PshemK wrote:
> The thing is - it didn't get remapped. Now I have two containers mapping
> to the same range, both live:
>
> pshemk@ii:~$ lxc list
> +-+-+-+--++---+
> | NAME | STATE |
Hi, I'm not sure what the problem here is. LXD will copy the filesystem
mapped and will remap on demand if there's another sub{g,u}id range
allocated for LXD on the new host.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
On Thu, Jun 22, 2017 at 11:11:59PM -, Miroslav Los wrote:
> Our actual templates are based on the lxc-sshd template example that
> comes with lxc-templates. There, basically all the lxc is is bind-mounts
> for necessary paths from the host, obviously read-only:
The /dev bind-mount is
Hi Miroslav,
Yes, we've been hardening the console handling code quite a bit prior to
this release. It seems that you are on a read-only file system which
prevents LXC from removing the underlying "/dev/console" file that
already exists. LXC wants to remove this file since it wants to prevent
** 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/1699759
Title:
LXC Alpine template broken on ppc64le
Status in
** Changed in: lxd (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christia
On Thu, May 18, 2017 at 08:09:05AM -, Konstantinos Tsakalozos wrote:
> I can confirm that "ls -al /dev/dri/" within the lxc container shows the
> devices you expect. However, "lxc config show xen2" shows the devices
> section being empty.
This isn't a bug at all. :) You're adding a device to
I've used your exact profile now:
https://paste.ubuntu.com/24586449/
--
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/1690822
Title:
GPU device in lxc profile ignored?
Status
chb@conventiont|~
> lxc profile show dummy
config:
security.nesting: "true"
security.privileged: "true"
description: ""
devices:
gpu:
type: gpu
name: dummy
used_by:
- /1.0/containers/alp1
- /1.0/containers/alpgpu
--
You received this bug notification because you are a member of Ubuntu
I couldn't reproduce this behavior locally.
- We'd need the logs for the daemon and the corresponding containers in
question from /var/log/lxd/*, please.
- Please also show
cat /proc/1/mountinfo
from inside one of those containers that doesn't mount the gpu device.
--
You received this bug
** 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/1654676
Title:
lxc-user-nic d
LXD 2.13 doesn't include my fix
https://github.com/lxc/lxd/commit/6c6af18b4ab4720c802a61fa932179562446a4df
yet.
--
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/1686036
Title:
** Changed in: lxc (Ubuntu)
Status: In Progress => 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/1686036
Title:
strange behavior after restore snapshot
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/1686036
Title:
strange behavior after restore snapshot
Status in
** Changed in: lxc (Ubuntu)
Status: New => In Progress
** 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.
Would be good if we could also SRU that to Xenial as well since this is
likely what users will be using most of the time as image in their
container. Adding stgraber to this thread.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g.
10 systemd will lower it to 65536 since this value is hard-coded into
systemd.
I've pushed a patch to systemd upstream that will try to set
the nofile limit to the allowed kernel maximum. If
Reproducible. Can you please open this bug on github.
--
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/1686036
Title:
strange behavior after restore snapshot
Status in lxc
This is very likely not a LXD bug. I suspect this is
https://github.com/zfsonlinux/zfs/issues/5796 again which I reported to
ZFS upstream. I'll ping them about this again tomorrow and if I don't
hear back will take a look at this myself.
** Bug watch added: Github Issue Tracker for ZFS #5796
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
** 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 ap
Hi John,
hi Christian,
Sent a branch to lxc that should fix this issue:
https://github.com/lxc/lxc/pull/1519
** Changed in: lxc (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Note, that since a while LXC is sending SIGRTMIN+3 to systemd. So unless
systemd has changed it's shutdown/halt signal again LXC should send the
right signal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
On Tue, Jan 31, 2017 at 11:34:43AM +0100, Christian Brauner wrote:
> I've reproduced this on a fresh standard xenial instance with LXD
> 2.0.8 and also on a xenial instance with a patched glibc that reports
> ENODEV on ttyname{_r}() on a pty fd that does not exist:
&g
I've reproduced this on a fresh standard xenial instance with LXD
2.0.8 and also on a xenial instance with a patched glibc that reports
ENODEV on ttyname{_r}() on a pty fd that does not exist:
root@x:~# ./enodev_on_pty_in_different_namespace
ttyname(): The pty device might exist in a different
Hi, this is not a bug. What you want is to recursively bind-mount:
lxc.mount.entry = /home home none rbind,create=dir 0 0
Christian
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Hi,
Have you tried again after a while. I don't think that this is related to the
uid/gid mappings. In order for the download template to work you should have a
default lxc config for your unprivileged user configured which would list the
uid/gid mapping you want to use, e.g.
# Container
** Changed in: lxc (Ubuntu)
Status: In Progress => 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/1653725
Title:
lxc-android-config not starting on
** 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/1653725
Title:
lxc-android-config not starting on
** 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/1649582
Title:
lxc-start fails to start a unprivileged container -
Right, the cpuset bug is gone which was your main problem. Now the
only thing left to do should be:
chmod +x /home/sneetsher/.local
Please try again and report back. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
Ok, I think I may have clue. You're using lxcfs in version 2.0.4. This
version of lxcfs does not handle uninitialized cpuset hierarchies
which can happen when systemd does not allocate a per-user cgroup in
the cpuset controller. I fixed this in lxcfs 2.0.5 by reimplementing
the cgroup handling
Please attach the container config file and show or attache the output
of the following commands:
- grep cgroup /proc/1/mountinfo
- cat /proc/self/cgroup
- ls -al /sys/fs/cgroup
- lxcfs --version
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1623143
Title:
Linux container does not take same cpu
1 - 100 of 141 matches
Mail list logo
