1. 28 Apr, 2014 7 commits
  2. 15 Apr, 2014 1 commit
  3. 11 Apr, 2014 1 commit
  4. 09 Apr, 2014 4 commits
  5. 08 Apr, 2014 4 commits
  6. 07 Apr, 2014 4 commits
  7. 05 Apr, 2014 1 commit
    • lxc_spawn: initialize netpipe · 2f2623ec
      Serge Hallyn authored
      When rebooting an unprivileged container, netpipe starts out
      as not -1.  If count_veths somehow changed this could lead
      to trying to send data over nonexistent pipe.  (Ok can't
      *really* happen, as it currently stands, but it's an open
      end)
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
  8. 04 Apr, 2014 9 commits
  9. 03 Apr, 2014 1 commit
    • fix lxc-info printing duplicate lines · e2426f0b
      Dwight Engen authored
      When lxc-info's stdout is not line buffered (ie. "lxc-info -n foo |more")
      the first three lines will be duplicated. This is because c->get_ips()
      comes next and it forks and the child will exit() causing its fds to be
      closed which flushes out its (fork duplicated) stdio buffers. The lines are
      then duplicated when the parent actually gets around to flushing out its
      stdio. This causes problems for programs (such as the lxc-webpanel) which
      are popen()ing lxc-info.
      
      The fix here isn't necessarily the right one, but does show what the
      problem is. Seems like maybe we should fix this inside of get_ips(), for
      other API callers as well.
      Signed-off-by: 's avatarDwight Engen <dwight.engen@oracle.com>
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
  10. 02 Apr, 2014 6 commits
  11. 01 Apr, 2014 2 commits
    • fix lxc-console not working by default · 982b5959
      Guillaume ZITTA authored
      fix lxc-console not working by default
      Signed-off-by: 's avatarGuillaume ZITTA <lxc@zitta.fr>
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
    • apparmor: auto-generate the blacklist rules · 198b363f
      Serge Hallyn authored
      This uses the generate-apparmor-rules.py script I sent out some time
      ago to auto-generate apparmor rules based on a higher level set of
      block/allow rules.
      
      Add apparmor policy testcase to make sure that some of the paths we
      expect to be denied (and allowed) write access to are in fact in
      effect in the final policy.
      
      With this policy, libvirt in a container is able to start its
      default network, which previously it could not.
      
      v2: address feedback from stgraber
      	  put lxc-generate-aa-rules.py into EXTRA_DIST
      	  add lxc-test-apparmor, container-base and container-rules to .gitignore
      	  take lxc-test-apparmor out of EXTRA_DIST
      	  make lxc-generate-aa-rules.py pep8-compliant
      	  don't automatically generate apparmor rules
      	  This is only bc we can't be guaranteed that python3 will be
      	  available.
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>