Skip to content

Commit f34c1bf

Browse files
committed
config: Eliminate privileged escalation in containers
Now that all aspects of the Moodle envirnonment are in volumes, there is no longer a need for containers to run in privileged mode to cope with file permission issues.
1 parent 5ed836b commit f34c1bf

2 files changed

Lines changed: 0 additions & 3 deletions

File tree

compose/default.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@ name: $mname
22
services:
33
mariadb:
44
image: $MARIADB_IMAGE
5-
privileged: true
65
restart: unless-stopped
76
networks:
87
- backend
@@ -17,7 +16,6 @@ services:
1716
- db:/bitnami/mariadb/data
1817
moodle:
1918
image: $MOODLE_IMAGE
20-
privileged: true
2119
restart: unless-stopped
2220
ports:
2321
- $MOODLE_PORT:8080

libexec/mdl-restore.sh

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,6 @@ for mname in $mnames; do
182182
fi
183183
db_runner="${mname}_worker_db_restore"
184184
container_tool run -d --rm --name "$db_runner" \
185-
--privileged \
186185
-e MARIADB_ROOT_PASSWORD="${ROOT_PASSWORD:-password}" \
187186
-e MARIADB_USER="${DB_USERNAME:-moodleuser}" \
188187
-e MARIADB_PASSWORD="${DB_PASSWORD:-password}" \

0 commit comments

Comments
 (0)