853e955b62
We should not use such a long `HEALTHCHECK` `--interval` as first task check if happening after given time, and before healthcheck returns `0` – **task won't be available** to the Docker networks – meaning that Mattermost won't work until then even if it deployed correctly! And in Docker envs it happens often – that DB is available all the time, and just MM app is being updated. In this case even if we are healthy since 1s – we need to wait 5min until it goes online.
48 строки
1.3 KiB
Docker
48 строки
1.3 KiB
Docker
FROM alpine:3.11
|
|
|
|
# Some ENV variables
|
|
ENV PATH="/mattermost/bin:${PATH}"
|
|
ARG PUID=2000
|
|
ARG PGID=2000
|
|
ARG MM_PACKAGE="https://releases.mattermost.com/5.22.2/mattermost-5.22.2-linux-amd64.tar.gz?src=docker"
|
|
|
|
|
|
# Install some needed packages
|
|
RUN apk add --no-cache \
|
|
ca-certificates \
|
|
curl \
|
|
libc6-compat \
|
|
libffi-dev \
|
|
linux-headers \
|
|
mailcap \
|
|
netcat-openbsd \
|
|
xmlsec-dev \
|
|
tzdata \
|
|
&& rm -rf /tmp/*
|
|
|
|
# Get Mattermost
|
|
RUN mkdir -p /mattermost/data /mattermost/plugins /mattermost/client/plugins \
|
|
&& if [ ! -z "$MM_PACKAGE" ]; then curl $MM_PACKAGE | tar -xvz ; \
|
|
else echo "please set the MM_PACKAGE" ; fi \
|
|
&& addgroup -g ${PGID} mattermost \
|
|
&& adduser -D -u ${PUID} -G mattermost -h /mattermost -D mattermost \
|
|
&& chown -R mattermost:mattermost /mattermost /mattermost/plugins /mattermost/client/plugins
|
|
|
|
USER mattermost
|
|
|
|
#Healthcheck to make sure container is ready
|
|
HEALTHCHECK --interval=30s --timeout=10s \
|
|
CMD curl -f http://localhost:8065/api/v4/system/ping || exit 1
|
|
|
|
|
|
# Configure entrypoint and command
|
|
COPY entrypoint.sh /
|
|
ENTRYPOINT ["/entrypoint.sh"]
|
|
WORKDIR /mattermost
|
|
CMD ["mattermost"]
|
|
|
|
EXPOSE 8065 8067 8074 8075
|
|
|
|
# Declare volumes for mount point directories
|
|
VOLUME ["/mattermost/data", "/mattermost/logs", "/mattermost/config", "/mattermost/plugins", "/mattermost/client/plugins"]
|