1. 29 Jul, 2016 2 commits
  2. 28 Jul, 2016 4 commits
  3. 27 Jul, 2016 2 commits
  4. 26 Jul, 2016 2 commits
  5. 25 Jul, 2016 2 commits
  6. 23 Jul, 2016 2 commits
  7. 22 Jul, 2016 4 commits
    • Merge pull request #1094 from brauner/2016-07-22/fix_android_lxc_copy · 5429ec24
      Stéphane Graber authored
      lxc-copy: do not use mkostemp and dprintf
    • lxc-copy: do not use mkostemp and dprintf · a8e279fd
      Christian Brauner authored
      Fixes android builds:
      
      DSBINDIR=\"/data/lxc/lxc/sbin\"      -I/build/libcap/libcap/include/ -Wall -Werror -MT lxc_copy.o -MD -MP -MF $depbase.Tpo -c -o lxc_copy.o lxc_copy.c &&\
      	mv -f $depbase.Tpo $depbase.Po
      lxc_copy.c: In function 'mount_tmpfs':
      lxc_copy.c:834:2: error: implicit declaration of function 'mkostemp' [-Werror=implicit-function-declaration]
        fd = mkostemp(premount, O_CLOEXEC);
        ^
      lxc_copy.c:841:2: error: implicit declaration of function 'dprintf' [-Werror=implicit-function-declaration]
        ret = dprintf(fd, "#! /bin/sh\n"
        ^
      Signed-off-by: 's avatarChristian Brauner <cbrauner@suse.de>
    • Merge pull request #1093 from brauner/2016-07-22/use_priu64 · bdf278a1
      Stéphane Graber authored
      c/r: use PRIu64 format specifier
    • c/r: use PRIu64 format specifier · 9b945f13
      Christian Brauner authored
      Fixes build failures on arm:
      
      criu.c: In function ‘exec_criu’:
      criu.c:310:4: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’ [-Werror=format=]
          ret = sprintf(ghost_limit, "%lu", opts->user->ghost_limit);
          ^
      In file included from criu.c:42:0:
      log.h:285:9: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’ [-Werror=format=]
        struct lxc_log_locinfo locinfo = LXC_LOG_LOCINFO_INIT;  \
               ^
      criu.c:312:5: note: in expansion of macro ‘ERROR’
           ERROR("failed to print ghost limit %lu", opts->user->ghost_limit);
           ^
      Signed-off-by: 's avatarChristian Brauner <cbrauner@suse.de>
  8. 21 Jul, 2016 1 commit
  9. 20 Jul, 2016 8 commits
  10. 19 Jul, 2016 5 commits
  11. 18 Jul, 2016 4 commits
    • Merge pull request #1084 from brauner/2016-07-16/clone_on_tmpfs · 897dcac4
      Serge Hallyn authored
      lxc-copy: allow snapshots to be placed on tmpfs
    • lxc-copy: allow snapshots to be placed on tmpfs · 60a77c18
      Christian Brauner authored
      Place an ephemeral container started with -e flag on a tmpfs. Restrictions are
      that you cannot request the data to be kept while placing the container on a
      tmpfs, that either overlay or aufs backing storage must be used, and that the
      storage backend of the original container must be a directory.
      
      For ephemeral snapshots backed by overlay or aufs filesystems, a fresh tmpfs
      is mounted over the containers directory if the user requests it. This should
      be the easiest options. Anything else would require us to change the current
      mount-layout of overlay and aufs snapshots. (A standard overlay or aufs
      snapshot clone currently has the layout:
      
      	/var/lib/lxc/CLONE_SNAPSHOT/delta0      <-- upperdir
      	/var/lib/lxc/CLONE_SNAPSHOT/rootfs
      	/var/lib/lxc/CLONE_SNAPSHOT/olwork
      	/var/lib/lxc/CLONE_SNAPSHOT/olwork/work <-- workdir
      
      with the lowerdir being
      
      	/var/lib/lxc/CLONE_PARENT/rootfs
      
      The fact that upperdir and workdir are not placed in a common subfolder under
      the container directory has the consequence that we cannot simply mount a fresh
      tmpfs under upperdir and workdir because overlay expects them to be on the same
      filesystem.)
      
      Because we mount a fresh tmpfs over the directory of the container the updated
      /etc/hostname file created during the clone residing in the upperdir (currently
      named "delta0" by default) will be hidden. Hence, if the user requests that the
      old name is not to be kept for the clone, we recreate this file on the tmpfs.
      This should be all that is required to restore the exact behaviour we would get
      with a normal clone.
      NOTE: If the container is rebooted all changes made to it are lost. This is not
      easy to prevent since each reboot remounts the rootfs again.
      Signed-off-by: 's avatarChristian Brauner <cbrauner@suse.de>
    • Set up MTU for vlan-type interfaces. · b4fb7de1
      Vitaly Lavrov authored
      Signed-off-by: 's avatarVitaly Lavrov <vel21ripn@gmail.com>
  12. 15 Jul, 2016 2 commits
  13. 13 Jul, 2016 1 commit
  14. 12 Jul, 2016 1 commit
    • c/r: drop in-flight connections during CRIU dump · f1954503
      Adrian Reber authored
      Shortly after CRIU 2.3 has been released a patch has been added to skip
      in-flight TCP connections. In-flight connections are not completely
      established connections (SYN, SYN-ACK). Skipping in-flight TCP
      connections means that the client has to re-initiate the connection
      establishment.
      
      This patch stores the CRIU version detected during version check, so
      that during dump/checkpoint options can be dynamically enabled depending
      on the available CRIU version.
      
      v2:
         * use the newly introduced criu version interface
         * add an option to disable skipping in-flight connections
      Signed-off-by: 's avatarAdrian Reber <areber@redhat.com>