From d7e06867f8ab33f2d1218af08bf92b86b01e31ea Mon Sep 17 00:00:00 2001 From: Steve Shipway Date: Thu, 2 Jun 2016 06:20:19 +1200 Subject: [PATCH] Remove option to set Privileged mode, as this cannot be parameterised in the docker-compose YAML (#162) --- templates/janitor/2/docker-compose.yml | 1 - templates/janitor/2/rancher-compose.yml | 7 +------ 2 files changed, 1 insertion(+), 7 deletions(-) diff --git a/templates/janitor/2/docker-compose.yml b/templates/janitor/2/docker-compose.yml index ecb8268..2a014ff 100644 --- a/templates/janitor/2/docker-compose.yml +++ b/templates/janitor/2/docker-compose.yml @@ -11,7 +11,6 @@ cleanup: io.rancher.scheduler.global: "true" io.rancher.scheduler.affinity:host_label_ne: "${EXCLUDE_LABEL}" net: none - privileged: ${PRIVILEGED_MODE} tty: false stdin_open: false volumes: diff --git a/templates/janitor/2/rancher-compose.yml b/templates/janitor/2/rancher-compose.yml index ad7a06e..81b347d 100644 --- a/templates/janitor/2/rancher-compose.yml +++ b/templates/janitor/2/rancher-compose.yml @@ -28,9 +28,4 @@ default: "*:*" required: false type: "string" - - variable: "PRIVILEGED_MODE" - label: "Run janitor in privileged mode" - description: "In hardened environments containers must be privileged to access the bind-mounted unix:///var/run/docker.sock. This is not the default case." - default: false - required: true - type: "boolean" +