|
@@ -4,8 +4,6 @@ package restrict
|
|
|
|
|
|
import (
|
|
import (
|
|
"fmt"
|
|
"fmt"
|
|
- "os"
|
|
|
|
- "path/filepath"
|
|
|
|
"syscall"
|
|
"syscall"
|
|
|
|
|
|
"github.com/dotcloud/docker/pkg/system"
|
|
"github.com/dotcloud/docker/pkg/system"
|
|
@@ -23,26 +21,5 @@ func Restrict() error {
|
|
if err := system.Mount("/dev/null", "/proc/kcore", "", syscall.MS_BIND, ""); err != nil {
|
|
if err := system.Mount("/dev/null", "/proc/kcore", "", syscall.MS_BIND, ""); err != nil {
|
|
return fmt.Errorf("unable to bind-mount /dev/null over /proc/kcore")
|
|
return fmt.Errorf("unable to bind-mount /dev/null over /proc/kcore")
|
|
}
|
|
}
|
|
-
|
|
|
|
- // This weird trick will allow us to mount /proc read-only, while being able to use AppArmor.
|
|
|
|
- // This is because apparently, loading an AppArmor profile requires write access to /proc/1/attr.
|
|
|
|
- // So we do another mount of procfs, ensure it's write-able, and bind-mount a subset of it.
|
|
|
|
- if err := os.Mkdir(".proc", 0700); err != nil {
|
|
|
|
- return fmt.Errorf("unable to create temporary proc mountpoint .proc: %s", err)
|
|
|
|
- }
|
|
|
|
- if err := system.Mount("proc", ".proc", "proc", 0, ""); err != nil {
|
|
|
|
- return fmt.Errorf("unable to mount proc on temporary proc mountpoint: %s", err)
|
|
|
|
- }
|
|
|
|
- if err := system.Mount("proc", ".proc", "", syscall.MS_REMOUNT, ""); err != nil {
|
|
|
|
- return fmt.Errorf("unable to remount proc read-write: %s", err)
|
|
|
|
- }
|
|
|
|
- for _, path := range []string{"attr", "task"} {
|
|
|
|
- if err := system.Mount(filepath.Join(".proc", "1", path), filepath.Join("proc", "1", path), "", syscall.MS_BIND, ""); err != nil {
|
|
|
|
- return fmt.Errorf("unable to bind-mount %s: %s", path, err)
|
|
|
|
- }
|
|
|
|
- }
|
|
|
|
- if err := system.Unmount(".proc", 0); err != nil {
|
|
|
|
- return fmt.Errorf("unable to unmount temporary proc filesystem: %s", err)
|
|
|
|
- }
|
|
|
|
- return os.RemoveAll(".proc")
|
|
|
|
|
|
+ return nil
|
|
}
|
|
}
|