1. 02 Jul, 2016 1 commit
    • cgfsng: don't pre-calculate path · 0b6ca6e3
      Serge Hallyn authored
      First, we're doing this so long a there is any cgroup config item -
      even if no devices ones.  Then if devices is not available we fail.
      This was leading to Rob E's mysterious startup failures.
      
      Secondly, we're not even using this info.  The user was removed
      awhile back.
      Signed-off-by: 's avatarSerge Hallyn <serge@hallyn.com>
  2. 29 Jun, 2016 4 commits
  3. 28 Jun, 2016 4 commits
  4. 27 Jun, 2016 7 commits
  5. 24 Jun, 2016 2 commits
  6. 23 Jun, 2016 2 commits
  7. 21 Jun, 2016 2 commits
  8. 18 Jun, 2016 2 commits
  9. 13 Jun, 2016 2 commits
    • Merge pull request #1047 from brauner/mips_container · f6578a7b
      Stéphane Graber authored
      lxc-debian: allow to specify a binfmt interpreter
    • lxc-debian: allow to specify a binfmt interpreter · d50cebd6
      Laurent Vivier authored
      If you specify an interpreter path with "-I" or "--interpreter-path",
      the architecture of the debian container can differ from the one of
      the host.
      
      Before creating the container, binfmt must be configured on the host:
      the script checks the name of the interpreter in /proc/sys/fs/binfmt_misc/
      to know where to install it in the container.
      
      To create a MIPS container on an x86_64 host:
      
      $ cat /proc/sys/fs/binfmt_misc/qemu-mips
      enabled
      interpreter //qemu-mips
      flags: OC
      offset 0
      magic 7f454c4601020100000000000000000000020008
      mask ffffffffffffff00fffffffffffffffffffeffff
      
      $ sudo lxc-create -n virtmips-stretch -t debian -- \
                       --arch=mips \
                       --interpreter-path=./mips-linux-user/qemu-mips \
                       --mirror=http://ftp.debian.org/debian \
                       --release=stretch
      Signed-off-by: 's avatarLaurent Vivier <laurent@vivier.eu>
  10. 09 Jun, 2016 2 commits
  11. 07 Jun, 2016 2 commits
  12. 06 Jun, 2016 2 commits
  13. 03 Jun, 2016 2 commits
    • Merge pull request #1040 from odyssey4me/include_apt_transport_https · 9d54166c
      Stéphane Graber authored
      Move apt-transport-https to global packages_template
    • Move apt-transport-https to global packages_template · d0e206b8
      Jesse Pretorius authored
      In many environments the preference is to configure containers with
      apt mirrors that are SSL-secured.
      
      When building containers using the download template this can't be
      done unless an insecure mirror is first used to install the
      apt-transport-https package, then the sources reconfigured to
      use the https URL.
      
      When building containers without using the download template this
      can't be done unless the container creator specifically includes
      this package in the package list at build time. It seems more
      intuitive to me to have the package installed by default.
      
      Commit 396f75ab added the package
      to the minbase variant, but this variant is not used by the download
      template build process. The build process instead specifies no
      variant, so this patch moves the package from the packages_template
      package list in the minbase variant to the global packages_template
      package list, ensuring that this package is included in all Ubuntu
      build images that use the lxc-ubuntu template.
      Signed-off-by: 's avatarJesse Pretorius <jesse.pretorius@rackspace.co.uk>
  14. 02 Jun, 2016 2 commits
  15. 31 May, 2016 4 commits