1. 20 Jan, 2010 1 commit
  2. 18 Jan, 2010 4 commits
  3. 14 Jan, 2010 5 commits
  4. 13 Jan, 2010 8 commits
  5. 08 Jan, 2010 9 commits
  6. 05 Jan, 2010 1 commit
  7. 28 Dec, 2009 1 commit
    • add macvlan vepa and bridge mode · e892973e
      Daniel Lezcano authored
      The future kernel 2.6.33 will incorporate the macvlan bridge
      mode where all the macvlan will be able to communicate if they are
      using the same physical interface. This is an interesting feature
      to have containers to communicate together. If we are outside of the
      container, we have to setup a macvlan on the same physical interface than
      the containers and use it to communicate with them.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  8. 27 Dec, 2009 4 commits
    • busybox template · eb960fea
      Daniel Lezcano authored
      This script builds a busybox rootfs and provides the associated
      configuration to run the busybox.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • adapt lxc-sshd to be a template · 418c73ad
      Daniel Lezcano authored
      Cleanup the script, simplify it and pass the arguments to this
      script to be callable by lxc-create template logic.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • add template option for lxc-create · 1b6d8e71
      Daniel Lezcano authored
      The lxc-create command is now able to call a sub script to install
      a mini template.
      Right now, debian is supported.
      
      The rootfs is stored automatically in <lxcpath>/<name>/rootfs
      So the rootfs is a subdirectory of the container configuration directory.
      
      When lxc-destroy is called, the rootfs is deleted with the container
      configuration.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • cleanup lxc-debian script · fb7460fe
      Daniel Lezcano authored
      The lxc-debian is epurated and consolidated with a better
      error handling.
      
      This script is no longer interactive but it installs in a specified
      place the debian rootfs.
      
      This script is not supposed to be called directly so it will fall in
      libexec path very soon. This script is called by lxc-create
      as a template with the right option and the right place.
      
      The debian network configuration is by dhcp.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  9. 18 Dec, 2009 1 commit
  10. 15 Dec, 2009 3 commits
  11. 26 Nov, 2009 3 commits
    • fix a compilation warning · 108ed092
      Daniel Lezcano authored
      lxc_get_cgroup_path is used in the file but the header
      defining the function is missing.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • "Default" configuration may destroy host system · f2ae79a0
      Andrian Nord authored
      If you're running (by mistake or typo) (via lxc-start) container that does not
      exists it will run with lxc.rootfs=/, meaning that /sbin/init will
      restart initialization procedure, efficiently messing host's system,
      that may lead to unpredictable results or even destroy (make inaccessible) host
      system (by reseting network configuration or something like that).
      
      (Actually, it _did_ destroy system of everyone who tested this).
      
      Actually, I finally lost any meaning of having such a feature for
      full-system containers. You may not use hosts's FS - it's described at
      above. You may not use some temporary directory - that's nonsense.
      
      This patch forbinds starting container via lxc-start without rcfile and
      custom start program, but probably it fixes only small part of problem.
      I really don't see much sense in such a feature without ability of
      overriding 'default' setting with command line switches. Anyway, default
      behaviour should be as save as possible.
      Signed-off-by: 's avatarAndrian Nord <NightNord@gmail.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • pass lxc_conf to the lxc_start function instead of the rcfile · fae349da
      Daniel Lezcano authored
      The rcfile is parsed in the lxc_start function. This is not the place
      to do that. Let's the caller to do that.
      
      In the meantime, we have the lxc_conf structure filled right before
      calling the lxc_start function so we can do some sanity check on the
      configuration to not break the system when we launch the container.
      
      Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>