** Also affects: cgmanager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cgmanager (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
** Changed in: cgmanager (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1355966
Title:
[FFE] Implement AbandonScope
Thanks for reporting this bug. I'm not sure it's actually a dup of
1240757, because the syslog seems to indicate that dnsmasq is offering
addresses over lxcbr0.
Could you do 'lxc-start -n container0 -l trace -o debug.out' and attach
debug.out here?
** Changed in: lxc (Ubuntu)
Status: New
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
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/1367730
Title:
container root directory has broken permissions with
Thanks. Meanwhile I've raised the issue on lxc-devel mailing list.
--
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/1367730
Title:
container root directory has broken
Hi,
your .JPG shows that there is a login prompt. The plymouth messages
should be harmless. Do you have any actual problems with the container,
i.e. cannot login or console is locked up?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307829
Title:
/run/netns/* gets umounted on the host when
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1299944
Title:
lxc-container-default-with-nesting is too lax
(lowered priority per guidelines since there is a workaround)
--
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/1346815
Title:
lxc-clone causes duplicate MAC address and IP
The bug was introduced by incomplete support for unexpanded
configuration which itself existed to prevent expanding of included
configuration files.
It is fixed in upstream lxc (tested), though I'm not sure exactly when this
(alpha2) is expected to hit the archive.
Note that a further fix is the
The fix for this is applied in lxc's git HEAD.
** Changed in: lxc (Ubuntu)
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/1307215
Title:
Thanks for reporting this bug. I'm afraid snapshotting is currently not
compatible with LVM. In the short term we should simply refuse snapshots
for lvm-backed containers. In the longer term, we'll need the lvm backing
store to provide a different naming scheme for snapshots, and its own
I don't see a /etc/init/serial.conf in my trusty or utopic hosts. Is
that only intalled on ppc hosts?
** No longer affects: qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Hi James,
does setting lxc.network.mtu = 9000 in the container configuration file
work?
Depending on how juju creates the containers, you may be able to simply
add that line to the bottom of /etc/lxc/default.conf to get the desired
result.
--
You received this bug notification because you are
I'm assigning myself as I do intend to do this work, but if someone else
works on it, please take the bug or comment on status here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
/systemd1/unit/session_2dc7_2escope
Whlie the cgroup is being autoremoved when empty, the more important
bug is that StopSession won't forcibly kill the cgroup. These methods
should be added at some point.
** Affects: systemd-shim (Ubuntu)
Importance: Medium
Assignee: Serge Hallyn
Thanks for the information. Indeed, lxc-stop -k still works by talking
to the lxc monitor. What appears to have happened here is that the
monitor itself is frozen.
Could you please show full output of:
ps -ef
Then do 'ps -ef | grep lxc-start' to find the lxc-start process for the
hung
Public bug reported:
Currently if you run a container with lxc-container-default-with-
nesting profile, you can run privileged containers inside that, but not
unprivileged containers. The special cases we add for /var/lib/lxc
should also be added for $HOME/.local/share/lxc.
** Affects: lxc
Public bug reported:
The lxc-user-nic program is a setuid-root program to create veth nics
and hook them to the host bridge and unprivileged containers. It should
run under a very tight apparmor profile.
(Make sure to test with ovs bridges as well, as its call-out to ovs-
vsctl may have
The minimal PATH comes from
getconf -a | grep ^PATH
(if confstr were not available then lxc would actually default to a
longer PATH)
status: invalid
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Looks like the value actually comes straight from a #define in the glibc
source code.
As such, I think it would be pretty reasonable to change lxc to always
use its own path.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: Invalid =
** Changed in: lxc
Importance: Undecided = High
** Changed in: lxc
Status: New = Triaged
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: lxc
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Sounds like a good idea, thanks.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Triaged
--
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)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Triaged
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You
(Ubuntu)
Status: New = Confirmed
** Also affects: debconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mysql-5.5 (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
** Information type changed from Private to Public
--
You received this bug notification
Thanks I'll do some testing. I suspect we'll need to allow access to
cgmanager, but otherwise this looks good.
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member
Since you're not restricting dbus, cgmanager is actually unaffected, so
this shouldn't restrict nested use at all.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thanks for submitting this bug.
To be clear,
'sudo ip link add type veth'
also returns an error?
Could you tell us which ami and which machine type you used to start the
amazon instance?
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
** Package changed: lxc (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Description changed:
+ =
+ ec2-run-instances ami-3021fb58 -t m1.small
+
+ ssh into the instance,
+
+ sudo ip link add type veth
+
+
thanks for reporting this bug.
Could you please show:
1. The result of 'netstat -x | grep lxc'
2. ps -ef | grep lxc
status: incomplete
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Quoting Nikola Krzalic (nik...@krzalic.com):
Looks like the lxc-start command got stuck, after killing the process
everything went back to normal.
...
still, I find it a bit strange that not even lxc-ls was working properly
Right, we should find a way to keep lxc-stop and lxc-ls from
Thanks for reporting this bug. To fix the cgmanager issue, add the line
lxc.mount.auto = cgroup:mixed
to your container configuration file.
That shouldn't explain your hang however. Assuming it doesn't, please
run
lxc-start -n container -l trace -o debug.out -- /sbin/init debug
verbose
Thanks for submitting this bug
status: confirmed
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
A proposed fix has been sent to the mailing list, and will probably be
applied in utopic today. In the meantime you can work around this by
using the 'append_config_item' method instead of set_config_item. (Note
that the C API does not have this same behavior, so this is only for the
python
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
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/1376717
** Changed in: lxc (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1357103
Title:
apparmor denied a golang build inside a
Thanks. This'll need to be fixed in the lxc.preinst.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: lxc (Ubuntu)
Status: New = 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/1355813
Title:
LXC containers reset bridge MTU on start/restart
Thanks for the bug report and the patch. I'm a bit concerned about
supporting this. I understand why you want it, but lxc in general won't
work well with a read-only cache, so an install failure early on would
seem preferable to a lxc-create failure later on.
Would using an overlayfs of the
It actually seems like a bug in aa-status.
Note that /sys/kernel/security/apparmor/profiles is not readable by non-
root users on the host. Yet non-root users on the host do not see a
python traceback when they run 'aa-status --enable'. This also suggests
that a container should not provide
Public bug reported:
Building libvirt in vivid currently results in qemuxml2argvtest failing.
It says that it expected a '\\V' and got a 'V'
Downgrading by doing
dpkg -i libxml2_2.9.1+dfsg1-3ubuntu4.4_amd64.deb
allows the build to complete.
** Affects: libxml2 (Ubuntu)
Importance:
Hi,
the no such process message at sendmsg in cgmanager.log suggests that
cgmanager has died. Could you edit /etc/default/cgmanager to have the
line
cgmanager_opts=--debug
then restart cgmanager, reproduce this, and upload the whole log?
Is this happening inside a container that has a
Quoting Chris West (1391...@bugs.launchpad.net):
Public bug reported:
The presence of /var/lock/lxc-net causes service lxc-net start to
claim success but actually just do nothing useful.
When the system goes down hard, /var/lock/lxc-net is not removed, fair
/var/lock should be a tmpfs.
(Marked as affecting cgmanager since cgmanager seems to be dying, but
need more info to debug)
** Also affects: cgmanager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cgmanager (Ubuntu)
Status: New = Confirmed
** Changed in: cgmanager (Ubuntu)
Importance:
Quoting Jason Harley (ja...@breqwatr.com):
I'm also curious about an update on this issue. I'm running 14.04.1,
Kernel 3.13.0-39-generic and LXC 1.0.6-0ubuntu0.1. 'strace' output of
open-scsi looks basically the same as above.
As I understand it, this is related to iSCSI's Netlink
I am pushing lxc_1.1.0~alpha2-0ubuntu7 which should fix this bug. I'm
hoping someone will SRU the patch to T and U.
Note that any container which actually specifies the securityfs mount in
its config (as the default unprivileged ubuntu configs do) should not
have this problem.
--
You received
** 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/1389244
Title:
lxc-info output different in terminal and file
I believe what is happening is that some of the api bindings are forking
with un-flushed data in the stdout buffer; then the data gets printed
on exit by each thread.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
Thank you for the update.
status: invalid
** Changed in: lxc (Ubuntu)
Status: Incomplete = 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/1391452
Title:
Ah, the ecryptfs $HOME might be the problem. I haven't tested that
and wouldn't be surprised if ecryptfs prevented the console from
looking ok. Could you try something like:
rm -rf $HOME/.config/lxc $HOME/.local/share/lxc
sudo mkdir /opt/lxc
sudo chown -R $USER /opt/lxc
mkdir /opt/lxc/config
Quoting Adam Ryczkowski (adam.ryczkow...@statystyka.net):
I really don't know how to tell you, which Trusty's 64bit minimal cd I
The full url.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Lowering to recommends would be sensible.
status: confirmed
importance: medium
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Given that it is commented on the same line, it shouldn't be
confusing. The reason it is done this way is so that postinst
can update /etc/default/lxc-net without affect /etc/default/lxc,
and without overriding any admin-provided configuration. There
are other ways we could do this, but this is
The relevant lines in /etc/default/lxc are:
USE_LXC_BRIDGE=false # overridden in lxc-net
[ -f /etc/default/lxc-net ] . /etc/default/lxc-net
while /etc/defalut/lxc-net does not source any other scripts. So
there is no other place you should need to look.
This will probably change during the
Thanks - the solution in your comment #1 would be good, if it was
accompanied by a /etc/init/lxc-dnsmasq.conf which had 'start on started
lxc-net; stop on stopping lxc-net; instance $BRIDGE
** Changed in: lxc (Ubuntu)
Importance: Undecided = Low
** Changed in: lxc (Ubuntu)
Status: New
@James,
the bug was incomplete because the question in comment #2 was never
answered until comment #4.
So it sounds like something juju needs to do through lxc config - if
there is anything sane that you can think of htat lxc can do to help,
please let us know.
** Changed in: lxc (Ubuntu)
Is this only happening when systemd is in the container, or when systemd
is on the host?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148
Title:
Re/starting an lxc
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
It appears that as tyhicks pointed out this is a dup of bug 1350947.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
James if you'd like to increase the priority of bug 1350947 please do
so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
hah, as pointed out in comment #4 of that bug. Marking this as a dup
** This bug has been marked a duplicate of bug 1350947
apparmor: no working rule to allow making a mount private
--
You received
Apparmor is recognizing make-slave', not slave. While apparmor will
be updated to accept 'slave' we should update the lxc policies to use
'make-slave' in the meantime.
Assigning this to Stéphane as he hasn't yet had a chance to show me the new
git-dpm packaging process :)
** Changed in: lxc
Was not able to reproduce this on my utopic host or a trusty VM. James
will try to come up with a reproducer.
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member
So the problem for you is that juju creates the containers with the
wrong mtu?
I don't know where juju gets its config file, (that it passes to 'lxc-
create -f but the best solution appears to be to update that to set the
mtu before the containers are ever created.
** Also affects: juju (Ubuntu)
Thanks for reporting this bug.
If there is a simple way to reproduce this (spin up ami-xx on
amazon and do 'juju deploy whatzit), please show it here.
Which release are you on, and which ppas do you have installed?
What do the following show:
dpkg -l | egrep -e
** 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/1402763
Title:
Multicast traffic not propating
@Andreas,
yes that's definately what it sounds like.
--
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/1357103
Title:
apparmor denied a golang build inside a container
Thanks for the information. The term.log has entries like
files list file for package `netcat-traditional' contains empty filename
which do suggest you have corrupted package index. Please try doing
sudo apt-get clean
before doing the
sudo apt-get update sudo apt-get -y dist-upgrade sudo
** Changed in: lxc (Ubuntu)
Status: Incomplete = 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/1261338
Title:
lxc-stop and even lxc-stop -k can hang
Status in
I'm afraid it seems your /var/lib/dpkg/status file is corrupted. Please
attach that file to this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/1356743
Title:
The Status: purge ok installed on the three netcat packages is not
right. Could you please try:
sudo cp /var/lib/dpkg/status /var/lib/dpkg/status.orig
sudo sed -i 's/purge ok installed/install ok installed/' /var/lib/dpkg/status
and see if that helps? Hopefully that is the only error and you
Which tutorial are you referring to?
Quoting clara (claranoehrin...@yahoo.fr):
Someone on a forum orientated me toward this tutorial. As I suppose you
know much more about Ubuntu than anyone else on these forums I'm
wondering if you think this way would help or not?
--
You received this bug
Please make sure that lxc.kmsg = 0 in your container configuration file
for systemd guests.
--
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/1347020
Title:
trusty host - utopic
Please show us the contents of /var/log/apt/term.log, /etc/lsb-release,
/etc/lxc/lxc-net.conf, /etc/default/lxc*, /usr/sbin/policy-rc.d, and the
results of 'uname -a', 'dpkg -l | grep lxc', and 'ls -l /sbin/init'.
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** 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/1347020
It's worth a shot. Please let us know if it did work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/1356743
Title:
package libcap2 1:2.22-1ubuntu3 failed to
affects: apparmor
** Also affects: apparmor
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/1350947
Title:
apparmor: no working
*** This bug is a duplicate of bug 1355966 ***
https://bugs.launchpad.net/bugs/1355966
** This bug has been marked a duplicate of bug 1355966
Implement AbandonScope (etc)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: systemd-shim (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1355966
Title:
Implement AbandonScope (etc)
Status
*** This bug is a duplicate of bug 1346815 ***
https://bugs.launchpad.net/bugs/1346815
** This bug has been marked a duplicate of bug 1346815
lxc-clone causes duplicate MAC address and IP address
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Summary changed:
- Implement AbandonScope (etc)
+ [FFE] Implement AbandonScope (etc)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1355966
Title:
[FFE]
Hi,
the systemd-shim with cgmanager was intended for use with systemd 208
(currently in debian experimental). Can you try building and installing
that and see if that fixes it for you? If it does we'll need to tighten
the packaging for systemd-shim to rely on the newer systemd. (You may
need
I'm building a version of 208 in ppa:serge-hallyn/systemd; I will try
to reproduce your issue with that on a utopic desktop vm. Assuming I
can reproduce it I should be able to easily figure out the problem.
** Changed in: systemd-shim (Ubuntu)
Importance: Undecided = High
** Changed in:
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = 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/1307215
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** 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.
You're getting the error message about multiple profiles because of the
extra 'lxc-defaulte' file, which presumably defines the same profile as
is defined in lxc-default. Remove that file and the load should go
fine.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received
Great, thanks for the information.
ecryptfs is a stackable filesystem, meaning that it sits between a real
filesystem and your view of it, interpreting (encrypting/decrypting)
data. There are several things which are notably difficult for a
stackign filesystem to get right.
I'm going to mark
@Max,
I don't see cgmanager specified in the gdb log.
ICould you still try comment #38?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1377332
Title:
[TOPBLOCKER] UI
Well, lxc-net doesn't support instances - yet :)
But you're right we dont' need that at this point. My point was that your
example didn't seem to have dnsmasq at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
(marking low priority for lxc because ther eis a workaround)
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Quoting Adam Ryczkowski (adam.ryczkow...@statystyka.net):
For one thing, the lxc-create can check if it is going to create a
user-space container on top of the ecryptfs, and warn the user if
True. Though I would prefer not to work around the bug like this
until we are certain that it cannot
I tried to reproduce this with a program doing an endless loop of
1000 forks which each immediately exit, while doing an endless loop
of cgm gettasks, all inside a container. I failed to get any cgproxy
crashes or hangs however.
Will keep trying tomorrow.
--
You received this bug notification
Hi,
thanks for submitting this bug. Is your host architecture armhf? If not,
then when using the download template you'll need to manually install
qemu-user-static on the host, and copy /usr/bin/qemu-arm-static into
the container's rootfs. The easier way to create such a container,
currently,
A set of packages with the proposed fix is at:
http://people.canonical.com/~serge/cgmanager-gettasks-race/
Could you please install those and let us know whether they fix the
issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Right so the bug her eis that your session-c2.scope was created without
giving you ownership of the directory and the tasks and cgroup.procs
files. Manually changing those permissions fixes it for me.
So this may actually be a regression in systemd itself.
--
You received this bug notification
** Package changed: lxc (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
** Summary changed:
- lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid
requestUser
Hi James,
to verify that this is a dup of bug 1413927, could you please
1. update your host to get lxcfs 0.4 :)
2. cat /proc/self/cgroup, get your name=systemd cgroup
3. under /sys/fs/cgroup/systemd/$(yourcgroup) chown your cgroup (i.e.
/user.slice/user-1000.slice/session-c2.scope) and the
Quoting Martin Pitt (martin.p...@ubuntu.com):
Stéphane Graber [2015-01-25 17:15 -]:
How are we supposed to run a systemd container on such a system then?
systemd in a container will need to create sub-entries in the
name=systemd controller.
Yes, that works fine, as the cgroup
*** This bug is a duplicate of bug 1413927 ***
https://bugs.launchpad.net/bugs/1413927
** This bug has been marked a duplicate of bug 1413927
user lxc containers fail to start under systemd: login name=systemd cgroup
is not owned by user
--
You received this bug notification because you
Sorry, I don't quite understand your questions. What do you mean by
running under the root? What is the problem at this point? If
you're getting an error creating unprivileged containers (which are
created/started without becoming the root user), see Basic unprivileged
usage at
Thanks for reporting this bug.
From the dpkgterminallog:
/usr/sbin/service: 118: /usr/sbin/service: Cannot fork
That sounds like a bigger problem than lxc. I don't see anything in the
syslog pointing to a kernel fault though.
Have you seen any more problems (related to lxc or otherwise) since
1 - 100 of 693 matches
Mail list logo
