1. 01 Feb, 2011 5 commits
  2. 27 Jan, 2011 2 commits
    • Fix paths in the lxc-busybox template · b09ecaf3
      Daniel Lezcano authored
      Author of the patch : Jonathan Liu <???> posted as a bug fix on the lxc
      sourceforge website.
      
      OS: Arch Linux 32-bit
      
      /etc/init.d/rcS do not use full path to syslogd, mount and udhcpc executables.
      As busybox requires /proc mounted if CONFIG_BUSYBOX_EXEC_PATH="/proc/self/exe"
      to run these commands without full path, the full path should be used in the
      startup script as /proc is mounted later in the script.
      
      It also fails to start the machine if /lib64 does not exist on the host system
      as there is a mount entry for /lib64 in the config.
      
      The attached patch changes commands in /etc/init.d/rcS to use full path and
      adds a check for /lib64 on host before adding lib64 mount entries to config.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • export env variable in lxc_start · 3244e750
      Daniel Lezcano authored
      Let's export the 'container' variable and let init receive it
      as a kernel command line option.
      
      In the upstart init scripts, we can distinguish if we are in a
      container context or not.
      
      ===============================================================================
      
      # /dev/console - getty
      #
      # This service maintains a getty on /dev/console from the point the
      # system is started until it is shut down again.
      # It only runs in lxc containers.
      
      start on stopped rc RUNLEVEL=[2345]
      stop on runlevel [!2345]
      
      env container
      pre-start script
      	[ "x$container" != "xlxc" ] && { stop; exit 0; }
      	exit 0;
      end script
      
      respawn
      
      exec /sbin/getty -8 38400 /dev/console
      
      ===============================================================================
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  3. 23 Jan, 2011 1 commit
    • suppress udev log output · 434d90db
      Daniel Lezcano authored
      We use udev within these containers and we prevent the /dev files
      to be created with the cgroup whitelist. So when the udevd receives
      the event from the kernel, it will fail to create some nodes in /dev
      and will spit error on the console.
      
      We set the log level to zero, so udev will silently fail.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  4. 22 Jan, 2011 1 commit
    • Update ubuntu templates · 27b39fd4
      Serge Hallyn authored
      Rename 'ubuntu' template to 'lucid'
      
      Add new maverick and natty templates, which do much less tweaking
      of the environment.  These should only be used on a kernel which
      supports sysfs tagging for /sys/class/net, as udev will be running
      in the container.
      
      The natty template needed to slightly change the installed packages
      for dhclient to be correclty installed.
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@canonical.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  5. 18 Jan, 2011 1 commit
  6. 17 Jan, 2011 2 commits
  7. 16 Jan, 2011 1 commit
    • Fix mntflags initialization · 91656ce5
      Joerg Gollnick authored
      Dear all,
      while setting up a container on x86_64 (archlinux host/guest) I had trouble 
      with mounting dev/pts and others from container.fstab and a ssh login does not 
      work (only ssh container bash -i gives you a shell)
      The cause is that conf.c does not initialize mntflags.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  8. 14 Jan, 2011 1 commit
  9. 13 Jan, 2011 7 commits
  10. 10 Jan, 2011 1 commit
  11. 09 Jan, 2011 1 commit
    • fix the ns_cgroup vs clone_children · 5193cc3d
      Daniel Lezcano authored
      The following patch fixes the bug where the clone_children compatibility
      flag is available with the ns_cgroup subsystem. The 2.6.37 kernel version
      should be the only one which is concerned by this modification, please
      refer to Documentation/feature-removal-schedule.txt and look for ns_cgroup.
      
      The problem is coming from we check for clone_children and we set it
      automatically and then we try to create a new cgroup. As the
      ns_cgroup is present the cgroup already exists and we are not allowed
      to attach our pid to a new cgroup. The next error will be when we try
      to create a new container because we enabled the clone_children flag
      and the ns_cgroup is present, it is not allowed by the kernel.
      
      The patch fix this by checking the mount options.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  12. 28 Dec, 2010 7 commits
  13. 17 Dec, 2010 7 commits
  14. 30 Oct, 2010 1 commit
  15. 26 Oct, 2010 2 commits