From c30872027ca3f237b3cb4eca60b2681be62f076d Mon Sep 17 00:00:00 2001 From: Sam Thursfield Date: Tue, 9 Jun 2015 12:30:31 +0100 Subject: Note that chroot backend has been tested on OSX now. Also, remove a comment that I think is superfluous. Hopefully it's still clear that the chroot backend should work on any POSIX OS. --- sandboxlib/chroot.py | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/sandboxlib/chroot.py b/sandboxlib/chroot.py index e224ec0..127bbab 100644 --- a/sandboxlib/chroot.py +++ b/sandboxlib/chroot.py @@ -18,8 +18,8 @@ This implements an API defined in sandboxlib/__init__.py. This backend should work on any POSIX-compliant operating system. It has been -tested on Linux only. The calling process must be able to use the chroot() -syscall, which is likely to require 'root' priviliges. +tested on Linux and Mac OS X. The calling process must be able to use the +chroot() syscall, which is likely to require 'root' priviliges. If any 'extra_mounts' are specified, there must be a working 'mount' binary in the host system. @@ -86,11 +86,6 @@ def process_mount_config(mounts, extra_mounts): def process_network_config(network): - # It'd be possible to implement network isolation on Linux using the - # clone() syscall. However, I prefer to have the 'chroot' backend behave - # the same on all platforms, and have separate Linux-specific backends to - # do Linux-specific stuff. - assert network == 'undefined', \ "'%s' is an unsupported value for 'network' in the 'chroot' backend. " \ "Network sharing cannot be be configured in this backend." % network -- cgit v1.2.1