ERROR when starting mattermost , postgres and nginx read_only file system #39
Comments
craph
changed the title
|
After more investigations, it seems the errors are due to the tmpfs entries in docker-compose files. Postgres and nginx are both based on alpine. In alpine, tmpfs:
- /run # instead of /var/runIf you want, I can do a PR for that ? What do you think @mrckndt , @jasonblais |
This was referenced Oct 12, 2021
|
Hi @jasonblais is it possible to have some updates on this issue and PR ? |
|
@mrckndt, @cpanato, @hanzei, After more investigations, the errors are due to the tmpfs entries in docker-compose files. Postgres and nginx are both based on alpine. In alpine, tmpfs:
- /run # instead of /var/runHere are the steps to reproduce the behavior : # lsb_release -d
Description: CentOS Linux release 7.7.1908 (Core)
# docker --version
Docker version 19.03.6, build 369ce74a3c
# docker-compose version
docker-compose version 1.26.0, build unknown
docker-py version: 4.2.1
CPython version: 3.6.8
OpenSSL version: OpenSSL 1.0.2k-fips 26 Jan 2017
# cat .env
# Domain of service
DOMAIN=mymmserver.com
# Container settings
## Timezone inside the containers. The value needs to be in the form 'Europe/Berlin'.
## A list of these tz database names can be looked up at Wikipedia
## https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ=UTC
RESTART_POLICY=unless-stopped
# Postgres settings
## Documentation for this image and available settings can be found on hub.docker.com
## https://hub.docker.com/_/postgres
## Please keep in mind this will create a superuser and it's recommended to use a less privileged
## user to connect to the database.
## A guide on how to change the database user to a nonsuperuser can be found in docs/creation-of-nonsuperuser.md
POSTGRES_IMAGE_TAG=13-alpine
POSTGRES_DATA_PATH=./volumes/db/var/lib/postgresql/data
POSTGRES_USER=mmuser
POSTGRES_PASSWORD=mmuser_password
POSTGRES_DB=mattermost
# Nginx
## The nginx container will use a configuration found at the NGINX_MATTERMOST_CONFIG. The config aims
## to be secure and uses a catch-all server vhost which will work out-of-the-box. For additional settings
## or changes ones can edit it or provide another config. Important note: inside the container, nginx sources
## every config file inside */etc/nginx/conf.d* ending with a *.conf* file extension.
## Inside the container the uid and gid is 101. The folder owner can be set with
## `sudo chown -R 101:101 ./nginx` if needed.
NGINX_IMAGE_TAG=alpine
## The folder containing server blocks and any additional config to nginx.conf
NGINX_CONFIG_PATH=./nginx/conf.d
NGINX_DHPARAMS_FILE=./nginx/dhparams4096.pem
CERT_PATH=./volumes/web/cert/cert.pem
KEY_PATH=./volumes/web/cert/key-no-password.pem
#GITLAB_PKI_CHAIN_PATH=<path_to_your_gitlab_pki>/pki_chain.pem
#CERT_PATH=./certs/etc/letsencrypt/live/${DOMAIN}/fullchain.pem
#KEY_PATH=./certs/etc/letsencrypt/live/${DOMAIN}/privkey.pem
## Exposed ports to the host. Inside the container 80 and 443 will be used
HTTPS_PORT=4434
HTTP_PORT=8008
# Mattermost settings
## Inside the container the uid and gid is 2000. The folder owner can be set with
## `sudo chown -R 2000:2000 ./volumes/app/mattermost`.
MATTERMOST_CONFIG_PATH=./volumes/app/mattermost/config
MATTERMOST_DATA_PATH=./volumes/app/mattermost/data
MATTERMOST_LOGS_PATH=./volumes/app/mattermost/logs
MATTERMOST_PLUGINS_PATH=./volumes/app/mattermost/plugins
MATTERMOST_CLIENT_PLUGINS_PATH=./volumes/app/mattermost/client/plugins
## This will be 'mattermost-enterprise-edition' or 'mattermost-team-edition' based on the version of Mattermost you're installing.
MATTERMOST_IMAGE=mattermost-team-edition
MATTERMOST_IMAGE_TAG=6.1
## 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.
APP_PORT=8065
## Configuration settings for Mattermost. Documentation on the variables and the settings itself can be found at
## https://docs.mattermost.com/administration/config-settings.html
## Keep in mind that variables set here will take precedence over the same setting in config.json. This includes
## the system console as well and settings set with env variables will be greyed out.
## Below one can find necessary settings to spin up the Mattermost container
MM_SQLSETTINGS_DRIVERNAME=postgres
MM_SQLSETTINGS_DATASOURCE=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB}?sslmode=disable&connect_timeout=10
## Example settings (any additional setting added here also needs to be introduced in the docker-compose.yml)
MM_SERVICESETTINGS_SITEURL=https://${DOMAIN}:4434
postgres_mattermost | 2021-12-18 21:10:32.076 UTC [1] FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": Read-only file system
postgres_mattermost | 2021-12-18 21:10:32.078 UTC [1] LOG: database system is shut down
postgres_mattermost exited with code 1
...
nginx_mattermost | nginx: [emerg] open() "/var/run/nginx.pid" failed (30: Read-only file system)
nginx_mattermost exited with code 1Here a screenshot
|
|
Hello @mrckndt, Do you have any news about my PR ? Thank you very much. |
|
Closing as it's not valid anymore. Check here #53 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I just followed all the steps to start with a fresh installation of MM with the version 5.38.2 and when I ran docker-compose up -d I have errors with the database and nginx.
Here are the errors:
and for nginx :
I have existing certificate and key from a previous installation of MM 5.31.0 so I moved the file to the new directory.
Here is the .env file :
The text was updated successfully, but these errors were encountered: