Package: lxc
Version: 0.6.2-1
Severity: wishlist
The example lxc scripts (/usr/share/doc/lxc/examples/lxc-{debian,fedora}) that
create full distribution images depend on the cgroup features, and the error
messages if they are not enabled are not exactly helpful.
It would be good to document, probably in README.Debian, that you need to
mount the cgroup filesystem *somewhere*, but that it doesn't matter where.
As is evident from this discussion on the Debian developers list there is no
general agreement, but all the tools handle the situation sensibly by scanning
the mount table to find it:
http://thread.gmane.org/gmane.linux.debian.devel.general/135979/focus=135987
Perhaps some text akin to this would work?
The lxc container system supports using the cgroups kernel subsystem to
provide various limits, including restricting device access, CPU access and
CPU time slices. See lxc.conf(5) for full details of supported features.
To support this the cgroup virtual filesystem must be mounted somewhere, but
the exact location doesn't matter: lxc will scan /proc/mounts to find it
automatically.
An example fstab entry to mount the cgroup filesystem would be:
cgroup /var/local/cgroup cgroup defaults 0 0
For that to work you need to manually create the /var/local/cgroup directory,
as it is not automatically created.
Debian does not presently have a policy for the location of this subsystem.
For full details see the discussion here:
http://thread.gmane.org/gmane.linux.debian.devel.general/135979/focus=135987
Regards,
Daniel
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lxc depends on:
ii libc6 2.9-13 GNU C Library: Shared libraries
Versions of packages lxc recommends:
ii libcap2-bin 1:2.16-5 basic utility programs for using c
lxc suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]