1. 02 Mar, 2017 1 commit
  2. 27 Feb, 2017 2 commits
  3. 26 Feb, 2017 2 commits
  4. 25 Feb, 2017 1 commit
  5. 23 Feb, 2017 4 commits
  6. 22 Feb, 2017 1 commit
  7. 19 Feb, 2017 2 commits
  8. 18 Feb, 2017 6 commits
  9. 17 Feb, 2017 1 commit
  10. 16 Feb, 2017 1 commit
  11. 15 Feb, 2017 2 commits
  12. 12 Feb, 2017 3 commits
    • Merge pull request #1430 from ffontaine/master · 1f14c2ea
      Christian Brauner authored
      Add HAVE_LIBCAP
    • Add HAVE_LIBCAP · e37dda71
      Fabrice Fontaine authored
      Currently it is impossible to build lxc with --disable-capabilities if
      the user has libcap-dev installed on his system as:
       - calls to cap_xxx functions are not protected by HAVE_LIBCAP defines.
       The whole file is only protected by HAVE_SYS_CAPABILITY_H.
       - AC_CHECK_LIB default action-if-found is overriden by [true] so
       HAVE_LIBCAP is never written to config.h
      
      This patch replaces all HAVE_SYS_CAPABILITY_H checks by HAVE_LIBCAP
      checks (fix #1361)
      Signed-off-by: 's avatarFabrice Fontaine <fontaine.fabrice@gmail.com>
    • seccomp: allow x32 guests on amd64 hosts. · 11de80d6
      Adam Borowski authored
      Without this patch, x32 guests (and no others) worked "natively" with x32
      host lxc, but not on regular amd64 hosts.  That was especially problematic
      as a number of ioctls such as those needed by netfilter don't work in such
      scenarios, thus you want to run amd64 on the host.
      
      With the patch, you can use all three ABIs: i386 x32 amd64 on amd64 hosts.
      
      Despite x32 being little used, there's no reason to deny it by default:
      the admin needs to compile their own kernel with CONFIG_X86_X32=y or (on
      Debian) boot with syscall.x32=y.  If they've done so, it is a reasonable
      assumption they want x32 guests.
      Signed-off-by: 's avatarAdam Borowski <kilobyte@angband.pl>
  13. 08 Feb, 2017 4 commits
    • Merge pull request #1424 from brauner/2017-02-08/thomasDOTjaroschATintra2netDOTcom_pty_sigttou · 3a5cb1af
      Stéphane Graber authored
      lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals
    • Merge pull request #1425 from cebe/patch-1 · b93fbd24
      Stéphane Graber authored
      Make lxc-net return non-zero on failure
    • Make lxc-net return non-zero on failure · 4f4e7141
      Carsten Brandt authored
      I found that even though the service lxc-net failed to start because I made some wrong configuration
      settings the command exists zero.
      So systemd reports the status of the service as good even though it failed:
      
          # service lxc-net status
          ● lxc-net.service - LXC network bridge setup
             Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled)
             Active: active (exited) since Wed 2017-02-08 08:17:32 EST; 21min ago
            Process: 529 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-net start (code=exited, status=0/SUCCESS)
           Main PID: 529 (code=exited, status=0/SUCCESS)
             CGroup: /system.slice/lxc-net.service
      
          Feb 08 08:17:30 dvm2 systemd[1]: Starting LXC network bridge setup...
          Feb 08 08:17:32 dvm2 lxc-net[529]: dnsmasq: failed to create listening socket for 10.2.2.1: Address already in use
          Feb 08 08:17:32 dvm2 lxc-net[529]: Failed to setup lxc-net.
          Feb 08 08:17:32 dvm2 systemd[1]: Started LXC network bridge setup.
      
      Adding `exit 1` here makes it exit non-zero to make systemd recognize the failure.
      Signed-off-by: 's avatarCarsten Brandt <mail@cebe.cc>
    • lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals · 4dc96430
      Thomas Jarosch authored
      Prevent an endless loop while executing lxc-attach in the background:
      
      The kernel might fire SIGTTOU while an ioctl() in tcsetattr()
      is executed. When the ioctl() is resumed and retries,
      the signal handler interrupts it again.
      
      We can't configure the TTY to stop sending
      the signals in the first place since that
      is a modification/write to the TTY already.
      
      Still we clear the TOSTOP flag to prevent further signals.
      
      Command to reproduce the hang:
      ----------------------------
      cat > lxc_hang.sh << EOF
      /usr/bin/timeout 5s /usr/bin/lxc-attach -n SOMECONTAINER -- /bin/true
      EOF
      sh lxc_hang.sh    # hangs
      ----------------------------
      Signed-off-by: 's avatarThomas Jarosch <thomas.jarosch@intra2net.com>
  14. 07 Feb, 2017 2 commits
  15. 06 Feb, 2017 3 commits
  16. 02 Feb, 2017 5 commits
    • Merge pull request #1410 from brauner/2017-02-02/fix_compiler_error · 01b791a9
      Stéphane Graber authored
      conf/ile: make sure buffer is large enough
    • Merge pull request #1409 from tych0/setproctitle-comments · 9338493e
      Christian Brauner authored
      util: update setproctitle comments
    • Merge pull request #1398 from geaaru/lxc-sabayon · 0b5cbe35
      Stéphane Graber authored
      Add LXC template script of Sabayon OS
    • conf/ile: make sure buffer is large enough · 091045f8
      Christian Brauner authored
      conf.c: In function 'lxc_assign_network':
      conf.c:3096:25: error: '%lu' directive output may be truncated writing between 1 and 20 bytes into a region of size 19 [-Werror=format-truncation=]
         snprintf(pidstr, 19, "%lu", (unsigned long) pid);
                               ^~~
      conf.c:3096:24: note: using the range [1, 18446744073709551615] for directive argument
         snprintf(pidstr, 19, "%lu", (unsigned long) pid);
                              ^~~~~
      In file included from /usr/include/stdio.h:938:0,
                       from conf.c:35:
      /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 2 and 21 bytes into a destination of size 19
         return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              __bos (__s), __fmt, __va_arg_pack ());
              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      confile.c: In function 'network_new_hwaddrs':
      confile.c:2889:38: error: '%02x' directive output may be truncated writing between 2 and 8 bytes into a region of size 6 [-Werror=format-truncation=]
        snprintf(hwaddr, 18, "00:16:3e:%02x:%02x:%02x",
                                            ^~~~
      confile.c:2889:23: note: using the range [0, 4294967295] for directive argument
        snprintf(hwaddr, 18, "00:16:3e:%02x:%02x:%02x",
                             ^~~~~~~~~~~~~~~~~~~~~~~~~
      confile.c:2889:23: note: using the range [0, 4294967295] for directive argument
      In file included from /usr/include/stdio.h:938:0,
                       from confile.c:24:
      /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 18 and 36 bytes into a destination of size 18
         return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              __bos (__s), __fmt, __va_arg_pack ());
              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      Not sure whether the latter is really a problem. We might need an additional
      fix later on.
      Signed-off-by: 's avatarChristian Brauner <christian.brauner@ubuntu.com>
    • util: update setproctitle comments · 7d6c20f2
      Tycho Andersen authored
      Signed-off-by: 's avatarTycho Andersen <tycho.andersen@canonical.com>