This bug was fixed in the package lxc - 0.9.0-0ubuntu17
---
lxc (0.9.0-0ubuntu17) saucy; urgency=low
* 0011-cgroup-hook-handle-stricter-kernel: fix the mountcgroups hook in the
face of new restrictions imposed by the kernel on devices cgroups.
(LP: #1196518)
-- Serge
** Changed in: lxc (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument -
I'll post a patch to be less stringent about that check.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Ah, wait - the simpler solution would be for the mountcgroup hook to set
the device cgroup accesses (per the container config) before creating
${container}.real.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument - write
I'm testing this patch to solve the issue. So far it works on my
simplest case. I will run the lxc testsuite to check for some
regressions.
** Attachment added: 0011-cgroup-hook-handle-stricter-kernel
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I'm reopening because I can reproduce it on different hardware, but it
doesn't fail when running the same command twice and it seems a bit
racy. I'm searching for a way to reliably reproduce that problem.
** Changed in: lxc (Ubuntu)
Status: Invalid = Confirmed
** Changed in: lxc (Ubuntu)
This is reproducible on several systems, but only the 1rst time I start
a container when /sys/fs/cgroup/devices/lxc/NAME/ doesn't already
exist.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Tags added: apparmor apport-collected
** Description changed:
With kernel 3.10.0 lxc-create fails with the following error:
lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012'
is setup.
lxc-start 1372673552.852 DEBUGlxc_cgroup -
With otto from lp:otto I can reproduce the problem with the command:
$ sudo ./bin/otto -d create -u lp1196518-$RANDOM
~/iso/ubuntu/saucy-desktop-amd64.iso
The write(fd, value, strlen(value)) in do_cgroup_set in cgroup.c fails
with Invalid Argument
If the command is executed a second time with
For the moment, the workaround is to remove lxc.cgroup.devices.deny from
the config file, which is okay in our case since the machines are just
test hosts, but is not in the general case.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bot-stop-nagging
apport information
** Description changed:
With kernel 3.10.0 lxc-create fails with the following error:
lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012'
is setup.
lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called
for subsys devices
Here is a minimal test case to reproduce the problem:
NAME=test-deny-${RANDOM}
echo lxc.hook.mount = /usr/share/lxc/hooks/mountcgroups /tmp/${NAME}.lxc
lxc-create -t ubuntu -n $NAME -f /tmp/${NAME}.lxc -- -r saucy
lxc-start -n $NAME
From what I understand, setting devices.deny or .allow = a is
Marking invalid as I couldn't reproduce, and IIUC you will re-try with
fresh containers.
If you run into this again, please re-mark it new and do a 'apport-
collect 1196518'.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member
** Attachment added: fstab
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720321/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196518
Title:
** Attachment added: pre-mount.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720323/+files/pre-mount.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Attachment added: config
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720320/+files/config
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196518
Title:
** Attachment added: post-stop.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720322/+files/post-stop.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Attachment added: saucy-i386-20130701-1012.log.broken
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720325/+files/saucy-i386-20130701-1012.log.broken
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
** Attachment added: pre-start.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+attachment/3720324/+files/pre-start.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196518
Title:
lxc-start failed with lxc_cgroup - Invalid argument - write
22 matches
Mail list logo
