From a47ac18250aa14b0957da802db68f2cea78c71f8 Mon Sep 17 00:00:00 2001
From: Marco <mrckndt@riseup.net>
Date: Tue, 28 Sep 2021 13:58:35 +0200
Subject: [PATCH] Make readonly container overwritable, defaults to false

---
 docker-compose.yml | 2 +-
 env.example        | 5 +++++
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/docker-compose.yml b/docker-compose.yml
index 5874da0..0915626 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -34,7 +34,7 @@ services:
     security_opt:
       - no-new-privileges:true
     pids_limit: 200
-    read_only: true
+    read_only: ${MATTERMOST_CONTAINER_READONLY}
     tmpfs:
       - /tmp
     volumes:
diff --git a/env.example b/env.example
index 761ca20..84ab6a4 100644
--- a/env.example
+++ b/env.example
@@ -57,6 +57,11 @@ MATTERMOST_CLIENT_PLUGINS_PATH=./volumes/app/mattermost/client/plugins
 MATTERMOST_IMAGE=mattermost-enterprise-edition
 MATTERMOST_IMAGE_TAG=5.38
 
+## Make Mattermost container readonly. This interferes with the regeneration of root.html inside the container. Only use
+## it if you know what you're doing.
+## See https://github.com/mattermost/docker/issues/18
+MATTERMOST_CONTAINER_READONLY=false
+
 ## The app port is only relevant for using Mattermost without the nginx container as reverse proxy. This is not meant
 ## to be used with the internal HTTP server exposed but rather in case one wants to host several services on one host
 ## or for using it behind another existing reverse proxy.