Go to file
Serge Hallyn b98f7d6ed1 cgroups: rework to handle nested containers with multiple and partial mounts
Currently, if you create a container and use the mountcgruop hook,
you get the /lxc/c1/c1.real cgroup mounted to /.  If you then try
to start containers inside that container, lxc can get confused.
This patch addresses that, by accepting that the cgroup as found
in /proc/self/cgroup can be partially hidden by bind mounts.

In this patch:

Add optional 'lxc.cgroup.use' to /etc/lxc/lxc.conf to specify which
mounted cgroup filesystems lxc should use.  So far only the cgroup
creation respects this.

Keep separate cgroup information for each cgroup mountpoint.  So if
the caller is in devices cgroup /a but cpuset cgroup /b that should
now be ok.

Change how we decide whether to ignore failure to set devices cgroup
settings.  Actually look to see if our current cgroup already has the
settings.  If not, add them.

Finally, the real reason for this patch: in a nested container,
/proc/self/cgroup says nothing about where under /sys/fs/cgroup you
might find yourself.  Handle this by searching for our pid in tasks
files, and keep that info in the cgroup handler.

Also remove all strdupa from cgroup.c (not android-friendly).

Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
2013-08-14 10:51:01 -05:00
config configure/makefile: rename default_conf to distro_conf 2013-05-31 11:14:26 -05:00
doc lxc.conf.sgml.in: note the arguments and environment variables passed to hooks 2013-08-13 13:45:56 -05:00
hooks hooks/Makefile.am: add ubuntu-cloud-prep 2013-08-14 09:57:12 -05:00
src cgroups: rework to handle nested containers with multiple and partial mounts 2013-08-14 10:51:01 -05:00
templates add a clone hook for ubuntu-cloud images 2013-08-09 08:40:25 -05:00
.gitignore add lxc-user-nic 2013-08-14 10:50:37 -05:00
AUTHORS Initial revision 2008-08-06 14:32:29 +00:00
autogen.sh lxc: kill libtool 2009-10-22 15:33:40 +02:00
configure.ac lxc-user-nic: specify config and db files in autoconf 2013-08-14 10:50:46 -05:00
CONTRIBUTING Minor documentation updates 2012-12-06 00:02:36 -05:00
COPYING Minor documentation updates 2012-12-06 00:02:36 -05:00
INSTALL Minor documentation updates 2012-12-06 00:02:36 -05:00
lxc.pc.in fixes for rpmbuild 2011-09-13 15:08:04 +02:00
lxc.spec.in lxc.spec.in: remove lxc-shutdown (for commit 3e625e2d) 2013-05-29 09:03:49 -05:00
MAINTAINERS Change author email address 2013-03-19 11:19:13 +01:00
Makefile.am EXTRA_DIST: Fix missing files with "make dist" 2013-03-26 13:12:29 -04:00
NEWS Initial revision 2008-08-06 14:32:29 +00:00
README Update README w/ libcap troubleshooting tip. 2013-03-01 17:32:08 -05:00
runapitests.sh Update for consistent indent 2012-12-06 00:04:27 -05:00
TODO Remove all trailing whitespaces. 2012-11-26 12:08:13 -05:00

Please see the COPYING file for details on copying and usage.
Please refer to the INSTALL file for instructions on how to build.

What is lxc:

  The container technology is actively being pushed into the mainstream linux
  kernel. It provides the resource management through the control groups  aka
  process containers and resource isolation through the namespaces.

  The  linux  containers, lxc, aims to use these new functionalities to pro-
  vide an userspace container object which provides full  resource  isolation
  and resource control for an applications or a system.

  The first objective of this project is to make the life easier for the ker-
  nel developers involved in the containers project and  especially  to  con-
  tinue  working  on  the  Checkpoint/Restart  new features. The lxc is small
  enough to easily manage a container with simple command lines and  complete
  enough to be used for other purposes.

Using lxc:

  Refer the lxc* man pages (generated from doc/* files)

Downloading the current source code:

  Source for the latest released version can always be downloaded from
  http://lxc.sourceforge.net/download/lxc

  You can browse the up to the minute source code and change history online.
  http://lxc.git.sourceforge.net

  For an even more bleeding edge experience, you may want to look at the
  staging branch where all changes aimed at the next release land before
  getting pulled into the master branch.
  http://github.com/lxc/lxc

  For detailed build instruction refer to INSTALL and man lxc man page
  but a short command line should work:
  ./autogen.sh && ./configure && make && sudo make install
  preceded by ./autogen.sh if configure do not exist yet.

Troubleshooting:

  If the ./autogen.sh script shows the following message: "aclocal: not found",
  you are likely missing the "automake" package. Make sure it's installed and
  try again.

  If the ./configure script gives you the following message:
    "configure: error: Please install the libcap development files."
  you are likely missing the "libcap-dev" package.
  The configure script will usually give you hints as to what you are missing,
  looking for those in your package manager will usually give you the package
  that you need to install.

Getting help:

  when you find you need help, you can check out one of the two
  lxc mailing list archives and register if interested:
  https://lists.sourceforge.net/lists/listinfo/lxc-devel
  https://lists.sourceforge.net/lists/listinfo/lxc-users

Portability:

  lxc  is  still  in  development, so the command syntax and the API can
  change. The version 1.0.0 will be the frozen version.

  lxc is developed and tested on Linux since kernel mainline version 2.6.27
  (without network) and 2.6.29 with network isolation.
  It's compiled with gcc, and should work on most architectures as long as the
  required kernel features are available. This includes (but isn't limited to):
  i686, x86_64, ppc, ppc64, S390, armel and armhf.

AUTHOR
       Daniel Lezcano <daniel.lezcano@free.fr>

Seccomp with LXC
----------------

To restrict a container with seccomp, you must specify a profile which is
basically a whitelist of system calls it may execute.  In the container
config file, add a line like

lxc.seccomp = /var/lib/lxc/q1/seccomp.full

I created a usable (but basically worthless) seccomp.full file using

cat > seccomp.full << EOF
1
whitelist
EOF
for i in `seq 0 300`; do
    echo $i >> seccomp.full
done
for i in `seq 1024 1079`; do
    echo $i >> seccomp.full
done

 -- Serge Hallyn <serge.hallyn@ubuntu.com>  Fri, 27 Jul 2012 15:47:02 +0600