1. 08 Feb, 2017 1 commit
    • 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>
  2. 06 Feb, 2017 2 commits
  3. 02 Feb, 2017 7 commits
  4. 30 Jan, 2017 2 commits
  5. 29 Jan, 2017 3 commits
  6. 28 Jan, 2017 1 commit
  7. 27 Jan, 2017 2 commits
  8. 26 Jan, 2017 2 commits
    • Merge pull request #1392 from cjwatson/start-ephemeral-python32 · 42dc0de4
      Stéphane Graber authored
      Make lxc-start-ephemeral Python 3.2-compatible
    • Make lxc-start-ephemeral Python 3.2-compatible · e0e34b7e
      Colin Watson authored
      On Ubuntu 12.04 LTS with Python 3.2, `lxc-start-ephemeral` breaks as
      follows:
      
          Traceback (most recent call last):
            File "/usr/bin/lxc-start-ephemeral", line 371, in attach_as_user
            File "/usr/lib/python3.2/subprocess.py", line 515, in check_output
            File "/usr/lib/python3.2/subprocess.py", line 732, in __init__
          LookupError: unknown encoding: ANSI_X3.4-1968
      
      This is because `universal_newlines=True` causes `subprocess` to use
      `io.TextIOWrapper`, and in versions of Python earlier than 3.3 that
      fetched the preferred encoding using `locale.getpreferredencoding()`
      rather than `locale.getpreferredencoding(False)`, thereby changing the
      locale and causing codecs to be reloaded.  However, `attach_as_user`
      runs inside the container and thus can't rely on having access to the
      same Python standard library on disk.
      
      The workaround is to decode by hand instead, avoiding the temporary
      change of locale.
      Signed-off-by: 's avatarColin Watson <cjwatson@ubuntu.com>
  9. 21 Jan, 2017 2 commits
  10. 12 Jan, 2017 2 commits
  11. 11 Jan, 2017 2 commits
  12. 07 Jan, 2017 5 commits
  13. 04 Jan, 2017 6 commits
  14. 03 Jan, 2017 2 commits
  15. 29 Dec, 2016 1 commit