Go to file
Serge Hallyn 2e44ed1e64 lxc-ubuntu: use release-updates and release-security
Particularly for LTS releases, which many people will want to use in
their containers, it is not wise to not use -security and -updates.
Furthermore the fix allowing ssh to allow the container to shut down
is in lucid-updates only.

With this patch, after debootstrapping a container, we add -updates
and -security to sources.list and do an apt-get upgrade under chroot.
Unfortunately we need to do this because debootstrap doesn't know how
to.

Signed-off-by: Serge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>
2012-02-26 10:44:40 +01:00
config Add MIPS as a supported architecture 2012-02-26 00:49:48 +01:00
doc Add man page for lxc-attach 2012-02-23 09:57:14 +01:00
src fix-automake-1.13 2012-02-23 09:57:26 +01:00
templates lxc-ubuntu: use release-updates and release-security 2012-02-26 10:44:40 +01:00
.gitignore add lxc-archlinux template 2011-11-10 09:41:46 +01: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 fix-automake-1.13 2012-02-23 09:57:26 +01:00
CONTRIBUTING CONTRIBUTING: specify where one can send patches 2009-03-19 16:11:11 +01:00
COPYING Initial revision 2008-08-06 14:32:29 +00:00
INSTALL update INSTALL file 2010-05-10 11:50:09 +02:00
lxc.pc.in fixes for rpmbuild 2011-09-13 15:08:04 +02:00
lxc.spec.in fixes for rpmbuild 2011-09-13 15:08:04 +02:00
MAINTAINERS change repository url in MAINTAINERS 2010-05-28 17:39:11 +02:00
Makefile.am take into account new configure option --with-linuxdir 2011-02-01 12:54:17 +01:00
NEWS Initial revision 2008-08-06 14:32:29 +00:00
README README should not be a copy of lxc man page 2010-06-02 15:03:34 +02:00
RELEASE-NOTES Initial revision 2008-08-06 14:32:29 +00:00
TODO Add a TODO file 2009-02-12 14:46:54 +00: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 functionnalities 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 detailed build instruction refer to INSTALL and man lxc man page
  but a short command line should work:
  ./configure && make && sudo make install && sudo lxc-setcap
  preceded by ./autogen.sh if configure do not exist yet.

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.
  is compiled with gcc, and supports i686, x86_64, ppc, ppc64, S390 archi.

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