mattermost / mattermost-docker Goto Github PK

View Code? Open in Web Editor NEW

963.0 69.0 579.0 415 KB

Deprecated

License: Apache License 2.0

Shell 64.46% Dockerfile 35.54%

mattermost docker hacktoberfest

mattermost-docker's Introduction

Deprecated

Please see the guide on how to Install Mattermost via Docker.

mattermost-docker's People

Contributors

Stargazers

Watchers

Forkers

muto-y samnazarko tribemedia fmaker intfrr snyderra hauspie redspread wildcodeschool rogervaas jaekwon-park looper25 golaboratory mikefaille ruep r0ps3c ubc pwr-inf kenntwasde abnopanda anoland data-exp-lab psidium umdspacesystemslab dgoodwin hfarner floydianslips eungjun-yi andymac4182 vane-tech tobiastraxel mitel numericube it33 cavetech gspe piedoom pierreozoux tobatus gravufo space-curiosity reskohz absalan marcellovetro gongfupanada neven7 samdolan dariaphoebe nsaud01 ynoami bokazio hackur retsofaj ps00k tes backpackcoder savitojs sourceops karrots gacyun aozdemirci bamachrn chrber thomasf waynema02 nhumrich mobielabs rmoorman juguerre rothgar rl55 joshuacox mikemichel gorinovic cgenie pe46dro antonk5 elct9620 j-p-k remialvado kubeages codecraf8 ikaritw ademisinfo rskumar philipp-berger maackle columbusnests maxandersen gitrago rgaidot jasonblais msfwaifu dreambeam mecod loretoparisi jrx-vag banzo wzrdtales dextershin

mattermost-docker's Issues

PLATFORM_PORT_80_TCP_PORT can be overridden, but hostname of app cannot.

In the web setup, PLATFORM_PORT_80_TCP_PORT can be passed as an environment variable if we need to run the MM App on a different port. The docker_entry seds the APP Port in the nginx config.

However, the app is hard coded and forces this to be Docker Compose only.

Ideal: Default to docker compose ( a value of "app") but allow an ENV variable to be passed with the application hostname if we are using a different clustering technology with our own service discovery.

Note: the Database/App containers already do this with
(in App docker entry:)
DB_HOST=${DB_HOST:-db}
DB_PORT_5432_TCP_PORT=${DB_PORT_5432_TCP_PORT:-5432}

We could do the same thing:
APP_HOST=${APP_HOST:-app}
PLATFORM_PORT_80_TCP_PORT=${PLATFORM_PORT_80_TCP_PORT:-80}

and then when doing the sed in the docker_entry, fix both items.

Install on aws beanstalk

Any plans on update to lattermost 3.0.1 ?

I tried to update Dockerfile

FROM ubuntu:14.04

RUN apt-get update && apt-get -y install wget nectar
RUN mkdir -p /mattermost/data

RUN wget https://releases.mattermost.com/3.0.1/mattermost-team-3.0.1-linux-amd64.tar.gz \
        && tar -xvzf mattermost-team-3.0.1-linux-amd64.tar.gz && rm mattermost-team-3.0.1-linux-amd64.tar.gz

COPY config.template.json /
COPY docker-entry.sh /

RUN chmod +x /docker-entry.sh
ENTRYPOINT /docker-entry.sh

EXPOSE 80

And it launches ok, but when I change anything on System Console the system returns always this error:

We received an unexpected status code from the server. (500)

Also, this error appears many times in the system log:

[2016/05/17 01:02:36 UTC] [EROR] /api/v1/websocket: code=404 ip=[IP_ADDR]

Any hints ?

Not compatible with docker networks

Hey,
I tested your docker-compose file and it's not working with docker networks
I get repetitively the following error :
mattermost_1 | nc: getaddrinfo: Name or service not known.
Here is my docker-compose.yml if you need more information let me know.

version: '2'
services:
  db:
    build: db
    volumes:
    - ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
    - /etc/localtime:/etc/localtime:ro
  mattermost:
    build: app
    links:
      - db:db
    networks:
      - nginx
    volumes:
      - ./volumes/app/mattermost/config:/mattermost/config:rw
      - ./volumes/app/mattermost/data:/mattermost/data:rw
      - /etc/localtime:/etc/localtime:ro
networks:
  nginx:
    external: true

cycle-time / logs of activity ref WAL-E to S3

Eventhough I'm not using my mattermost installation that much, at present, as I'm still testing, I'm noticing a logging cycle of uploading / archiving to S3 every minute ... (see link below). Is this normal ... and if so, is there a way to increase the cycle time ... ie. to every 5 mins rather than every minute?

https://gist.github.com/Analect/4fc34398ff874d6172a426b43dd9ddc5

Thanks.

bad gateway

ok so i modified the host mattermost-ssl file and even the mattermost file. then dc build and dc up -d i still got an error about certs files not being found when inspecting the logs of the web container which stopped... so i docker cp'd those files into the container and now it runs and i even get redirected to https finally but see a bad gateway error from nginx

docker-entrypoint1.sh: no such file or directory

Versions:

docker-compose: 1.8.1
docker engine: 1.12.2
Ubuntu 16.04 LTS

docker-compose build fails with the following output (truncated for brevity):

...
Removing make (4.0-8.1) ...
Removing manpages-dev (3.74-1) ...
Removing manpages (3.74-1) ...
Removing patch (2.7.5-1) ...
Removing xz-utils (5.1.1alpha+20120614-2+b3) ...
Removing gcc-4.9 (4.9.2-10) ...
Removing binutils (2.25-5) ...
Removing cpp-4.9 (4.9.2-10) ...
Removing libgcc-4.9-dev:amd64 (4.9.2-10) ...
Removing libasan1:amd64 (4.9.2-10) ...
Removing libatomic1:amd64 (4.9.2-10) ...
Removing libcilkrts5:amd64 (4.9.2-10) ...
Removing libcloog-isl4:amd64 (0.18.2-1+b2) ...
Removing libgomp1:amd64 (4.9.2-10) ...
Removing libisl10:amd64 (0.12.2-2) ...
Removing libitm1:amd64 (4.9.2-10) ...
Removing liblsan0:amd64 (4.9.2-10) ...
Removing libmpc3:amd64 (1.0.2-1) ...
Removing libmpfr4:amd64 (3.1.2-2) ...
Removing libquadmath0:amd64 (4.9.2-10) ...
Removing libtsan0:amd64 (4.9.2-10) ...
Removing libubsan0:amd64 (4.9.2-10) ...
Processing triggers for libc-bin (2.19-18+deb8u6) ...
 ---> f81e3c262849
Removing intermediate container ea0334dde00d
Step 3 : ADD make_db.sh /docker-entrypoint-initdb.d/
 ---> 0d7f145dba24
Removing intermediate container 44f3a6962e44
Step 4 : ADD setup-wale.sh /docker-entrypoint-initdb.d/
 ---> cad2abdcaeaa
Removing intermediate container 504c64a8b84f
Step 5 : COPY docker-entrypoint1.sh /
ERROR: Service 'db' failed to build: stat /data/var/lib/docker/aufs/mnt/f6d3bd5fba89b069cebcf26761d7d5d421f03e8af44b99ca6b422ac81d7eb70b/docker-entrypoint1.sh: no such file or directory

Help With Setup

Thanks so much for creating this. I'm currently just trying to set this up on a Mac so I can see if it would be feasible in production. I'm fairly new to both docker and mattermost so I could really use some help. I'm not sure where to go to edit the listen address that mattermost is using for others to connect to.

For example in the one line install I was able to change my host file and point to dockerhost:8065. The only thing I'm finding here is something about 80:80 and that we shouldn't modify the listen address in the service settings.

Sorry for my ignorance. Am I to assume that the docker IP is the one that's being used? If so, I'm getting a failed to connect error. How can I change the settings and then how would I go about verifying that the service is running? I've tried putting in the IP, adding to my host file etc and still can't reach the mattermost build from the same Mac.

Any help would be appreciated.

how do i build fresh?

when i build and up -d i still wind up with same teams and users

Some assistance getting this up and running

@npcode
Thanks for putting together this repo.

I was having difficulty in getting it up and running and wanted to check a few things with you.

For the SSL certificate stuff, I followed the first part of this, in terms of generating a *.key and *.crt file ... and then renamed these as key-no-password.pem (putting it in /web/cert/private/) and cert.pem (putting in /web/cert/) respectively.
Is this the right approach in order to then work with your 'web' container here?
Running up postgres
For the 'volumes' references back on the host machine ...
- ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
Do these need any special permissioning?

The database is sluggish to start up, for some reason ... and gives a message that database wasn't properly shut down ... even when I'm creating a whole new container (rather than restarting an exising one).

LOG:  database system was interrupted; last known up at 2016-01-25 21:39:07 GMT
LOG:  incomplete startup packet
FATAL:  the database system is starting up
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  record with zero length at 0/17208E8
LOG:  redo is not required
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  incomplete startup packet
LOG:  received smart shutdown request
LOG:  autovacuum launcher shutting down
LOG:  database system was interrupted; last known up at 2016-01-25 21:55:41 GMT
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  record with zero length at 0/1720950
LOG:  redo is not required
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started

I explored (via docker-enter) the postgres container for other logs /var/log/postgresql, to see if that could give me some clues, but there were none, for some reason. Have they been disabled in a config file somewhere?

When the db looked like it was eventually up ... I restarted both app and web containers, just to be safe.

docker-compose restart app
docker-compose restart web

The app gave me back the following logs

Configure database connection...SKIP
Wait until database is ready...
Starting platform
panic: Failed to open sql connection pq: the database system is starting up

goroutine 1 [running]:
github.com/mattermost/platform/store.setupConnection(0xc13e50, 0x6, 0xc8201c8150, 0x8, 0xc820018ba0, 0x57, 0xa, 0xa, 0x415e00, 0xc820018c58)
    /go/src/github.com/mattermost/platform/store/sql_store.go:180 +0x5be
github.com/mattermost/platform/store.NewSqlStore(0x0, 0x0)
    /go/src/github.com/mattermost/platform/store/sql_store.go:59 +0x11c
github.com/mattermost/platform/api.NewServer()
    /go/src/github.com/mattermost/platform/api/server.go:31 +0xb5
main.main()
    /go/src/github.com/mattermost/platform/mattermost.go:66 +0x688

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
    /usr/local/go/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [syscall]:
os/signal.loop()
    /usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
    /usr/local/go/src/os/signal/signal_unix.go:28 +0x37

goroutine 7 [select]:
code.google.com/p/log4go.NewFileLogWriter.func1(0xc8200707e0)
    /go/src/github.com/mattermost/platform/Godeps/_workspace/src/code.google.com/p/log4go/filelog.go:84 +0xabc
created by code.google.com/p/log4go.NewFileLogWriter
    /go/src/github.com/mattermost/platform/Godeps/_workspace/src/code.google.com/p/log4go/filelog.go:116 +0x380

goroutine 8 [chan receive]:
database/sql.(*DB).connectionOpener(0xc82012bb80)
    /usr/local/go/src/database/sql/sql.go:634 +0x45
created by database/sql.Open
    /usr/local/go/src/database/sql/sql.go:481 +0x336
Configure database connection...SKIP
Wait until database is ready...
Starting platform
Configure database connection...SKIP
Wait until database is ready...
Starting platform

Does that look normal?

The web container logs just had:
Starting Nginx

Any input you might have to get this up and running would be greatly appreciated.
Thanks

Rename $DB_PORT_5432_TCP_PORT variable

I just deployed a Mattermost docker container and I lost some time figuring out why the container wasn't connecting to the DB. I used DB_PORT instead of unintuitive DB_PORT_5432_TCP_PORT in my docker run.

I think this variable should be renamed to something user-friendly with less redundancy, why not DB_PORT, DB_TCP_PORT or DB_PORT_TCP ? In the config.template.json the replaced string is DB_PORT anyway.

Also, those variable should be displayed in the echo of docker-entry.sh

echo "Wait until database is ready..."

could be:

echo "Wait until database $DB_HOST:$DB_PORT_5432_TCP_PORT is ready..."

It would make error diagnose a lot easier ;)

Upload image to Docker Hub

Do you plan to upload the image to docker hub? Currently I can only see https://hub.docker.com/r/mattermost/platform/ which does not support version 3.0.

Web proxy causing issues when behind another proxy.

Theres a long issue on the official Mattermost repository pointing out a bug.

I figured out that this isn't a problem with the Mattermost platform itself but with the docker stup provided by this setup.

I used the docker-compose file provided here. Because I'm running multiple applications on my host I set up a reverse proxy. This reverse proxy serves HTTPS to the clients but communicates over HTTP with the backend, so this web proxy isn't using SSL. And there is the point!

By using HTTP in the backend this web proxy detects HTTP and passes it with the X-Forwared-Proto header to the Mattermost platform/app where it causes issues (explained in the other thread).

I'm creating a PR with a workaround for this.
For me I just dropped the additional proxy and pass everything from the reverse proxy directly to the Mattermost app.

Web container bash variable $PLATFORM_PORT_80_TCP_ADDR

Hello guys!

I'm trying to deploy this instance, but in my environment, the web container can't find a variable called $PLATFORM_PORT_80_TCP_ADDR in the file docker-entry.sh, thus making nginx exit.

Please look at my fork in https://github.com/Psidium/mattermost-docker to see the changes I've done (mostly to address a issue I had with proxys in my corporate level).

Where this variable was supposed to come from?

thank you,
Psidium

Install on osx

Can't build - Python issue on "db" container

Hi,

I've got an error when trying to exec docker-compose build after cloning the repository. The error looks like this :

remi@ns3151751:~/mattermost/mattermost-docker$ git status
HEAD détachée sur 3.4.0
rien à valider, la copie de travail est propre
remi@ns3151751:~/mattermost/mattermost-docker$ docker-compose build
Building db
Step 1 : FROM postgres:9.4
9.4: Pulling from library/postgres
6a5a5368e0c2: Pull complete
193f770cec44: Pull complete
33647077f2ee: Pull complete
53bc65f84840: Pull complete
a4d3b0f1c16a: Pull complete
bdbe3c2ddbbd: Pull complete
6ce1015b914c: Pull complete
19631bdff29c: Pull complete
66adf788dd4c: Pull complete
79dc48693081: Pull complete
6121a13ba57c: Pull complete
Digest: sha256:9149f6309b83c9b99ae2e1ecab3e14a9662a1a8d0159320c24e34827ffe4c930
Status: Downloaded newer image for postgres:9.4
 ---> cd870518bdf0
Step 2 : RUN apt-get update     && apt-get install -y python-dev lzop pv daemontools curl build-essential     && curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | python     && pip install wal-e     && apt-get remove -y build-essential python-dev     && apt-get autoremove -y     && apt-get clean     && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
 ---> Running in fa6cf07e86ba
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Get:2 http://apt.postgresql.org jessie-pgdg InRelease [46.7 kB]
Ign http://httpredir.debian.org jessie InRelease
Get:3 http://httpredir.debian.org jessie-updates InRelease [142 kB]
Get:4 http://security.debian.org jessie/updates/main amd64 Packages [391 kB]
Get:5 http://httpredir.debian.org jessie Release.gpg [2,373 B]
Get:6 http://httpredir.debian.org jessie-updates/main amd64 Packages [17.6 kB]
Get:7 http://httpredir.debian.org jessie Release [148 kB]
Get:8 http://apt.postgresql.org jessie-pgdg/main amd64 Packages [106 kB]
Get:9 http://httpredir.debian.org jessie/main amd64 Packages [9,064 kB]
Get:10 http://apt.postgresql.org jessie-pgdg/9.4 amd64 Packages [1,708 B]
Fetched 9,983 kB in 3s (2,862 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  binutils ca-certificates cpp cpp-4.9 dpkg-dev fakeroot g++ g++-4.9 gcc
  gcc-4.9 libalgorithm-diff-perl libalgorithm-diff-xs-perl
  libalgorithm-merge-perl libasan1 libatomic1 libc-dev-bin libc6-dev
  libcilkrts5 libcloog-isl4 libcurl3 libdpkg-perl libexpat1-dev libfakeroot
  libfile-fcntllock-perl libgcc-4.9-dev libgomp1 libidn11 libisl10 libitm1
  liblsan0 liblzo2-2 libmpc3 libmpfr4 libpython-dev libpython2.7
  libpython2.7-dev libquadmath0 librtmp1 libssh2-1 libstdc++-4.9-dev
  libtimedate-perl libtsan0 libubsan0 linux-libc-dev make manpages
  manpages-dev patch python2.7-dev xz-utils
Suggested packages:
  binutils-doc cpp-doc gcc-4.9-locales daemontools-run runit debian-keyring
  g++-multilib g++-4.9-multilib gcc-4.9-doc libstdc++6-4.9-dbg gcc-multilib
  autoconf automake libtool flex bison gdb gcc-doc gcc-4.9-multilib
  libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan1-dbg
  liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libquadmath0-dbg
  glibc-doc libstdc++-4.9-doc make-doc man-browser ed diffutils-doc doc-base
The following NEW packages will be installed:
  binutils build-essential ca-certificates cpp cpp-4.9 curl daemontools
  dpkg-dev fakeroot g++ g++-4.9 gcc gcc-4.9 libalgorithm-diff-perl
  libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan1 libatomic1
  libc-dev-bin libc6-dev libcilkrts5 libcloog-isl4 libcurl3 libdpkg-perl
  libexpat1-dev libfakeroot libfile-fcntllock-perl libgcc-4.9-dev libgomp1
  libidn11 libisl10 libitm1 liblsan0 liblzo2-2 libmpc3 libmpfr4 libpython-dev
  libpython2.7 libpython2.7-dev libquadmath0 librtmp1 libssh2-1
  libstdc++-4.9-dev libtimedate-perl libtsan0 libubsan0 linux-libc-dev lzop
  make manpages manpages-dev patch pv python-dev python2.7-dev xz-utils
0 upgraded, 56 newly installed, 0 to remove and 3 not upgraded.
Need to get 71.5 MB of archives.
After this operation, 182 MB of additional disk space will be used.
Get:1 http://httpredir.debian.org/debian/ jessie/main libidn11 amd64 1.29-1+deb8u2 [136 kB]
Get:2 http://httpredir.debian.org/debian/ jessie/main libasan1 amd64 4.9.2-10 [195 kB]
Get:3 http://httpredir.debian.org/debian/ jessie/main libatomic1 amd64 4.9.2-10 [8,992 B]
Get:4 http://httpredir.debian.org/debian/ jessie/main libcilkrts5 amd64 4.9.2-10 [40.1 kB]
Get:5 http://httpredir.debian.org/debian/ jessie/main libisl10 amd64 0.12.2-2 [440 kB]
Get:6 http://httpredir.debian.org/debian/ jessie/main libcloog-isl4 amd64 0.18.2-1+b2 [61.8 kB]
Get:7 http://httpredir.debian.org/debian/ jessie/main librtmp1 amd64 2.4+20150115.gita107cef-1 [59.8 kB]
Get:8 http://httpredir.debian.org/debian/ jessie/main libssh2-1 amd64 1.4.3-4.1+deb8u1 [125 kB]
Get:9 http://httpredir.debian.org/debian/ jessie/main libcurl3 amd64 7.38.0-4+deb8u4 [259 kB]
Get:10 http://httpredir.debian.org/debian/ jessie/main libgomp1 amd64 4.9.2-10 [37.8 kB]
Get:11 http://httpredir.debian.org/debian/ jessie/main libitm1 amd64 4.9.2-10 [29.2 kB]
Get:12 http://httpredir.debian.org/debian/ jessie/main liblsan0 amd64 4.9.2-10 [92.8 kB]
Get:13 http://httpredir.debian.org/debian/ jessie/main liblzo2-2 amd64 2.08-1.2 [54.6 kB]
Get:14 http://httpredir.debian.org/debian/ jessie/main libmpfr4 amd64 3.1.2-2 [527 kB]
Get:15 http://httpredir.debian.org/debian/ jessie/main libpython2.7 amd64 2.7.9-2+deb8u1 [1,081 kB]
Get:16 http://httpredir.debian.org/debian/ jessie/main libc-dev-bin amd64 2.19-18+deb8u6 [238 kB]
Get:17 http://httpredir.debian.org/debian/ jessie/main libc6-dev amd64 2.19-18+deb8u6 [2,002 kB]
Get:18 http://httpredir.debian.org/debian/ jessie/main libexpat1-dev amd64 2.1.0-6+deb8u3 [126 kB]
Get:19 http://httpredir.debian.org/debian/ jessie/main linux-libc-dev amd64 3.16.36-1+deb8u1 [1,034 kB]
Get:20 http://httpredir.debian.org/debian/ jessie/main libmpc3 amd64 1.0.2-1 [39.3 kB]
Get:21 http://httpredir.debian.org/debian/ jessie/main libpython2.7-dev amd64 2.7.9-2+deb8u1 [18.6 MB]
Get:22 http://httpredir.debian.org/debian/ jessie/main cpp-4.9 amd64 4.9.2-10 [5,169 kB]
Get:23 http://httpredir.debian.org/debian/ jessie/main cpp amd64 4:4.9.2-2 [17.3 kB]
Get:24 http://httpredir.debian.org/debian/ jessie/main gcc-4.9 amd64 4.9.2-10 [5,352 kB]
Get:25 http://httpredir.debian.org/debian/ jessie/main g++-4.9 amd64 4.9.2-10 [21.4 MB]
Get:26 http://httpredir.debian.org/debian/ jessie/main g++ amd64 4:4.9.2-2 [1,530 B]
Get:27 http://httpredir.debian.org/debian/ jessie/main make amd64 4.0-8.1 [349 kB]
Get:28 http://httpredir.debian.org/debian/ jessie/main libtimedate-perl all 2.3000-2 [42.2 kB]
Get:29 http://httpredir.debian.org/debian/ jessie/main build-essential amd64 11.7 [7,114 B]
Get:30 http://httpredir.debian.org/debian/ jessie/main libfakeroot amd64 1.20.2-1 [44.7 kB]
Get:31 http://httpredir.debian.org/debian/ jessie/main fakeroot amd64 1.20.2-1 [84.7 kB]
Get:32 http://httpredir.debian.org/debian/ jessie/main libalgorithm-diff-perl all 1.19.02-3 [51.7 kB]
Get:33 http://httpredir.debian.org/debian/ jessie/main libalgorithm-merge-perl all 0.08-2 [13.5 kB]
Get:34 http://httpredir.debian.org/debian/ jessie/main libquadmath0 amd64 4.9.2-10 [129 kB]
Get:35 http://httpredir.debian.org/debian/ jessie/main libfile-fcntllock-perl amd64 0.22-1+b1 [36.4 kB]
Get:36 http://httpredir.debian.org/debian/ jessie/main libtsan0 amd64 4.9.2-10 [212 kB]
Get:37 http://httpredir.debian.org/debian/ jessie/main libubsan0 amd64 4.9.2-10 [82.4 kB]
Get:38 http://httpredir.debian.org/debian/ jessie/main manpages all 3.74-1 [997 kB]
Get:39 http://httpredir.debian.org/debian/ jessie/main libpython-dev amd64 2.7.9-1 [19.6 kB]
Get:40 http://httpredir.debian.org/debian/ jessie/main patch amd64 2.7.5-1 [109 kB]
Get:41 http://httpredir.debian.org/debian/ jessie/main xz-utils amd64 5.1.1alpha+20120614-2+b3 [221 kB]
Get:42 http://httpredir.debian.org/debian/ jessie/main binutils amd64 2.25-5 [3,516 kB]
Get:43 http://httpredir.debian.org/debian/ jessie/main libgcc-4.9-dev amd64 4.9.2-10 [2,066 kB]
Get:44 http://httpredir.debian.org/debian/ jessie/main python2.7-dev amd64 2.7.9-2+deb8u1 [290 kB]
Get:45 http://httpredir.debian.org/debian/ jessie/main python-dev amd64 2.7.9-1 [1,182 B]
Get:46 http://httpredir.debian.org/debian/ jessie/main gcc amd64 4:4.9.2-2 [5,136 B]
Get:47 http://httpredir.debian.org/debian/ jessie/main libstdc++-4.9-dev amd64 4.9.2-10 [1,121 kB]
Get:48 http://httpredir.debian.org/debian/ jessie/main libdpkg-perl all 1.17.27 [1,075 kB]
Get:49 http://httpredir.debian.org/debian/ jessie/main dpkg-dev all 1.17.27 [1,548 kB]
Get:50 http://httpredir.debian.org/debian/ jessie/main ca-certificates all 20141019+deb8u1 [204 kB]
Get:51 http://httpredir.debian.org/debian/ jessie/main curl amd64 7.38.0-4+deb8u4 [200 kB]
Get:52 http://httpredir.debian.org/debian/ jessie/main daemontools amd64 1:0.76-6 [57.6 kB]
Get:53 http://httpredir.debian.org/debian/ jessie/main libalgorithm-diff-xs-perl amd64 0.04-3+b1 [12.2 kB]
Get:54 http://httpredir.debian.org/debian/ jessie/main lzop amd64 1.03-3 [44.8 kB]
Get:55 http://httpredir.debian.org/debian/ jessie/main manpages-dev all 3.74-1 [1,865 kB]
Get:56 http://httpredir.debian.org/debian/ jessie/main pv amd64 1.5.7-2 [45.4 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 71.5 MB in 6s (11.5 MB/s)
Selecting previously unselected package libidn11:amd64.
(Reading database ... 12485 files and directories currently installed.)
Preparing to unpack .../libidn11_1.29-1+deb8u2_amd64.deb ...
Unpacking libidn11:amd64 (1.29-1+deb8u2) ...
Selecting previously unselected package libasan1:amd64.
Preparing to unpack .../libasan1_4.9.2-10_amd64.deb ...
Unpacking libasan1:amd64 (4.9.2-10) ...
Selecting previously unselected package libatomic1:amd64.
Preparing to unpack .../libatomic1_4.9.2-10_amd64.deb ...
Unpacking libatomic1:amd64 (4.9.2-10) ...
Selecting previously unselected package libcilkrts5:amd64.
Preparing to unpack .../libcilkrts5_4.9.2-10_amd64.deb ...
Unpacking libcilkrts5:amd64 (4.9.2-10) ...
Selecting previously unselected package libisl10:amd64.
Preparing to unpack .../libisl10_0.12.2-2_amd64.deb ...
Unpacking libisl10:amd64 (0.12.2-2) ...
Selecting previously unselected package libcloog-isl4:amd64.
Preparing to unpack .../libcloog-isl4_0.18.2-1+b2_amd64.deb ...
Unpacking libcloog-isl4:amd64 (0.18.2-1+b2) ...
Selecting previously unselected package librtmp1:amd64.
Preparing to unpack .../librtmp1_2.4+20150115.gita107cef-1_amd64.deb ...
Unpacking librtmp1:amd64 (2.4+20150115.gita107cef-1) ...
Selecting previously unselected package libssh2-1:amd64.
Preparing to unpack .../libssh2-1_1.4.3-4.1+deb8u1_amd64.deb ...
Unpacking libssh2-1:amd64 (1.4.3-4.1+deb8u1) ...
Selecting previously unselected package libcurl3:amd64.
Preparing to unpack .../libcurl3_7.38.0-4+deb8u4_amd64.deb ...
Unpacking libcurl3:amd64 (7.38.0-4+deb8u4) ...
Selecting previously unselected package libgomp1:amd64.
Preparing to unpack .../libgomp1_4.9.2-10_amd64.deb ...
Unpacking libgomp1:amd64 (4.9.2-10) ...
Selecting previously unselected package libitm1:amd64.
Preparing to unpack .../libitm1_4.9.2-10_amd64.deb ...
Unpacking libitm1:amd64 (4.9.2-10) ...
Selecting previously unselected package liblsan0:amd64.
Preparing to unpack .../liblsan0_4.9.2-10_amd64.deb ...
Unpacking liblsan0:amd64 (4.9.2-10) ...
Selecting previously unselected package liblzo2-2:amd64.
Preparing to unpack .../liblzo2-2_2.08-1.2_amd64.deb ...
Unpacking liblzo2-2:amd64 (2.08-1.2) ...
Selecting previously unselected package libmpfr4:amd64.
Preparing to unpack .../libmpfr4_3.1.2-2_amd64.deb ...
Unpacking libmpfr4:amd64 (3.1.2-2) ...
Selecting previously unselected package libpython2.7:amd64.
Preparing to unpack .../libpython2.7_2.7.9-2+deb8u1_amd64.deb ...
Unpacking libpython2.7:amd64 (2.7.9-2+deb8u1) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../libc-dev-bin_2.19-18+deb8u6_amd64.deb ...
Unpacking libc-dev-bin (2.19-18+deb8u6) ...
Selecting previously unselected package linux-libc-dev:amd64.
Preparing to unpack .../linux-libc-dev_3.16.36-1+deb8u1_amd64.deb ...
Unpacking linux-libc-dev:amd64 (3.16.36-1+deb8u1) ...
Selecting previously unselected package libc6-dev:amd64.
Preparing to unpack .../libc6-dev_2.19-18+deb8u6_amd64.deb ...
Unpacking libc6-dev:amd64 (2.19-18+deb8u6) ...
Selecting previously unselected package libexpat1-dev:amd64.
Preparing to unpack .../libexpat1-dev_2.1.0-6+deb8u3_amd64.deb ...
Unpacking libexpat1-dev:amd64 (2.1.0-6+deb8u3) ...
Selecting previously unselected package libpython2.7-dev:amd64.
Preparing to unpack .../libpython2.7-dev_2.7.9-2+deb8u1_amd64.deb ...
Unpacking libpython2.7-dev:amd64 (2.7.9-2+deb8u1) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../libquadmath0_4.9.2-10_amd64.deb ...
Unpacking libquadmath0:amd64 (4.9.2-10) ...
Selecting previously unselected package libtsan0:amd64.
Preparing to unpack .../libtsan0_4.9.2-10_amd64.deb ...
Unpacking libtsan0:amd64 (4.9.2-10) ...
Selecting previously unselected package libubsan0:amd64.
Preparing to unpack .../libubsan0_4.9.2-10_amd64.deb ...
Unpacking libubsan0:amd64 (4.9.2-10) ...
Selecting previously unselected package libmpc3:amd64.
Preparing to unpack .../libmpc3_1.0.2-1_amd64.deb ...
Unpacking libmpc3:amd64 (1.0.2-1) ...
Selecting previously unselected package manpages.
Preparing to unpack .../manpages_3.74-1_all.deb ...
Unpacking manpages (3.74-1) ...
Selecting previously unselected package patch.
Preparing to unpack .../patch_2.7.5-1_amd64.deb ...
Unpacking patch (2.7.5-1) ...
Selecting previously unselected package xz-utils.
Preparing to unpack .../xz-utils_5.1.1alpha+20120614-2+b3_amd64.deb ...
Unpacking xz-utils (5.1.1alpha+20120614-2+b3) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.25-5_amd64.deb ...
Unpacking binutils (2.25-5) ...
Selecting previously unselected package cpp-4.9.
Preparing to unpack .../cpp-4.9_4.9.2-10_amd64.deb ...
Unpacking cpp-4.9 (4.9.2-10) ...
Selecting previously unselected package cpp.
Preparing to unpack .../cpp_4%3a4.9.2-2_amd64.deb ...
Unpacking cpp (4:4.9.2-2) ...
Selecting previously unselected package libgcc-4.9-dev:amd64.
Preparing to unpack .../libgcc-4.9-dev_4.9.2-10_amd64.deb ...
Unpacking libgcc-4.9-dev:amd64 (4.9.2-10) ...
Selecting previously unselected package gcc-4.9.
Preparing to unpack .../gcc-4.9_4.9.2-10_amd64.deb ...
Unpacking gcc-4.9 (4.9.2-10) ...
Selecting previously unselected package gcc.
Preparing to unpack .../gcc_4%3a4.9.2-2_amd64.deb ...
Unpacking gcc (4:4.9.2-2) ...
Selecting previously unselected package libstdc++-4.9-dev:amd64.
Preparing to unpack .../libstdc++-4.9-dev_4.9.2-10_amd64.deb ...
Unpacking libstdc++-4.9-dev:amd64 (4.9.2-10) ...
Selecting previously unselected package g++-4.9.
Preparing to unpack .../g++-4.9_4.9.2-10_amd64.deb ...
Unpacking g++-4.9 (4.9.2-10) ...
Selecting previously unselected package g++.
Preparing to unpack .../g++_4%3a4.9.2-2_amd64.deb ...
Unpacking g++ (4:4.9.2-2) ...
Selecting previously unselected package make.
Preparing to unpack .../make_4.0-8.1_amd64.deb ...
Unpacking make (4.0-8.1) ...
Selecting previously unselected package libtimedate-perl.
Preparing to unpack .../libtimedate-perl_2.3000-2_all.deb ...
Unpacking libtimedate-perl (2.3000-2) ...
Selecting previously unselected package libdpkg-perl.
Preparing to unpack .../libdpkg-perl_1.17.27_all.deb ...
Unpacking libdpkg-perl (1.17.27) ...
Selecting previously unselected package dpkg-dev.
Preparing to unpack .../dpkg-dev_1.17.27_all.deb ...
Unpacking dpkg-dev (1.17.27) ...
Selecting previously unselected package build-essential.
Preparing to unpack .../build-essential_11.7_amd64.deb ...
Unpacking build-essential (11.7) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20141019+deb8u1_all.deb ...
Unpacking ca-certificates (20141019+deb8u1) ...
Selecting previously unselected package curl.
Preparing to unpack .../curl_7.38.0-4+deb8u4_amd64.deb ...
Unpacking curl (7.38.0-4+deb8u4) ...
Selecting previously unselected package daemontools.
Preparing to unpack .../daemontools_1%3a0.76-6_amd64.deb ...
Unpacking daemontools (1:0.76-6) ...
Selecting previously unselected package libfakeroot:amd64.
Preparing to unpack .../libfakeroot_1.20.2-1_amd64.deb ...
Unpacking libfakeroot:amd64 (1.20.2-1) ...
Selecting previously unselected package fakeroot.
Preparing to unpack .../fakeroot_1.20.2-1_amd64.deb ...
Unpacking fakeroot (1.20.2-1) ...
Selecting previously unselected package libalgorithm-diff-perl.
Preparing to unpack .../libalgorithm-diff-perl_1.19.02-3_all.deb ...
Unpacking libalgorithm-diff-perl (1.19.02-3) ...
Selecting previously unselected package libalgorithm-diff-xs-perl.
Preparing to unpack .../libalgorithm-diff-xs-perl_0.04-3+b1_amd64.deb ...
Unpacking libalgorithm-diff-xs-perl (0.04-3+b1) ...
Selecting previously unselected package libalgorithm-merge-perl.
Preparing to unpack .../libalgorithm-merge-perl_0.08-2_all.deb ...
Unpacking libalgorithm-merge-perl (0.08-2) ...
Selecting previously unselected package libfile-fcntllock-perl.
Preparing to unpack .../libfile-fcntllock-perl_0.22-1+b1_amd64.deb ...
Unpacking libfile-fcntllock-perl (0.22-1+b1) ...
Selecting previously unselected package libpython-dev:amd64.
Preparing to unpack .../libpython-dev_2.7.9-1_amd64.deb ...
Unpacking libpython-dev:amd64 (2.7.9-1) ...
Selecting previously unselected package lzop.
Preparing to unpack .../archives/lzop_1.03-3_amd64.deb ...
Unpacking lzop (1.03-3) ...
Selecting previously unselected package manpages-dev.
Preparing to unpack .../manpages-dev_3.74-1_all.deb ...
Unpacking manpages-dev (3.74-1) ...
Selecting previously unselected package pv.
Preparing to unpack .../archives/pv_1.5.7-2_amd64.deb ...
Unpacking pv (1.5.7-2) ...
Selecting previously unselected package python2.7-dev.
Preparing to unpack .../python2.7-dev_2.7.9-2+deb8u1_amd64.deb ...
Unpacking python2.7-dev (2.7.9-2+deb8u1) ...
Selecting previously unselected package python-dev.
Preparing to unpack .../python-dev_2.7.9-1_amd64.deb ...
Unpacking python-dev (2.7.9-1) ...
Setting up libidn11:amd64 (1.29-1+deb8u2) ...
Setting up libasan1:amd64 (4.9.2-10) ...
Setting up libatomic1:amd64 (4.9.2-10) ...
Setting up libcilkrts5:amd64 (4.9.2-10) ...
Setting up libisl10:amd64 (0.12.2-2) ...
Setting up libcloog-isl4:amd64 (0.18.2-1+b2) ...
Setting up librtmp1:amd64 (2.4+20150115.gita107cef-1) ...
Setting up libssh2-1:amd64 (1.4.3-4.1+deb8u1) ...
Setting up libcurl3:amd64 (7.38.0-4+deb8u4) ...
Setting up libgomp1:amd64 (4.9.2-10) ...
Setting up libitm1:amd64 (4.9.2-10) ...
Setting up liblsan0:amd64 (4.9.2-10) ...
Setting up liblzo2-2:amd64 (2.08-1.2) ...
Setting up libmpfr4:amd64 (3.1.2-2) ...
Setting up libpython2.7:amd64 (2.7.9-2+deb8u1) ...
Setting up libc-dev-bin (2.19-18+deb8u6) ...
Setting up linux-libc-dev:amd64 (3.16.36-1+deb8u1) ...
Setting up libc6-dev:amd64 (2.19-18+deb8u6) ...
Setting up libexpat1-dev:amd64 (2.1.0-6+deb8u3) ...
Setting up libpython2.7-dev:amd64 (2.7.9-2+deb8u1) ...
Setting up libquadmath0:amd64 (4.9.2-10) ...
Setting up libtsan0:amd64 (4.9.2-10) ...
Setting up libubsan0:amd64 (4.9.2-10) ...
Setting up libmpc3:amd64 (1.0.2-1) ...
Setting up manpages (3.74-1) ...
Setting up patch (2.7.5-1) ...
Setting up xz-utils (5.1.1alpha+20120614-2+b3) ...
update-alternatives: using /usr/bin/xz to provide /usr/bin/lzma (lzma) in auto mode
Setting up binutils (2.25-5) ...
Setting up cpp-4.9 (4.9.2-10) ...
Setting up cpp (4:4.9.2-2) ...
Setting up libgcc-4.9-dev:amd64 (4.9.2-10) ...
Setting up gcc-4.9 (4.9.2-10) ...
Setting up gcc (4:4.9.2-2) ...
Setting up libstdc++-4.9-dev:amd64 (4.9.2-10) ...
Setting up g++-4.9 (4.9.2-10) ...
Setting up g++ (4:4.9.2-2) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
Setting up make (4.0-8.1) ...
Setting up libtimedate-perl (2.3000-2) ...
Setting up libdpkg-perl (1.17.27) ...
Setting up dpkg-dev (1.17.27) ...
Setting up build-essential (11.7) ...
Setting up ca-certificates (20141019+deb8u1) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Setting up curl (7.38.0-4+deb8u4) ...
Setting up daemontools (1:0.76-6) ...
Setting up libfakeroot:amd64 (1.20.2-1) ...
Setting up fakeroot (1.20.2-1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode
Setting up libalgorithm-diff-perl (1.19.02-3) ...
Setting up libalgorithm-diff-xs-perl (0.04-3+b1) ...
Setting up libalgorithm-merge-perl (0.08-2) ...
Setting up libfile-fcntllock-perl (0.22-1+b1) ...
Setting up libpython-dev:amd64 (2.7.9-1) ...
Setting up lzop (1.03-3) ...
Setting up manpages-dev (3.74-1) ...
Setting up pv (1.5.7-2) ...
Setting up python2.7-dev (2.7.9-2+deb8u1) ...
Setting up python-dev (2.7.9-1) ...
Processing triggers for libc-bin (2.19-18+deb8u6) ...
Processing triggers for ca-certificates (20141019+deb8u1) ...
Updating certificates in /etc/ssl/certs... 174 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Collecting pip
  Downloading pip-8.1.2-py2.py3-none-any.whl (1.2MB)
Collecting setuptools
  Downloading setuptools-28.2.0-py2.py3-none-any.whl (467kB)
Collecting wheel
  Downloading wheel-0.29.0-py2.py3-none-any.whl (66kB)
Installing collected packages: pip, setuptools, wheel
Successfully installed pip-8.1.2 setuptools-28.2.0 wheel-0.29.0
Collecting wal-e
  Downloading wal-e-1.0.0.tar.gz (88kB)
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-DI97ai/wal-e/setup.py", line 19, in <module>
        raise RuntimeError('Python versions < 3.4 are not supported.')
    RuntimeError: Python versions < 3.4 are not supported.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-DI97ai/wal-e/
ERROR: Service 'db' failed to build: The command '/bin/sh -c apt-get update     && apt-get install -y python-dev lzop pv daemontools curl build-essential     && curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | python     && pip install wal-e     && apt-get remove -y build-essential python-dev     && apt-get autoremove -y     && apt-get clean     && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*' returned a non-zero code: 1

I've tried on both master and 3.4.0 tag. My host is on Ubuntu 16.04 and I've got other working containers on this host.
Any idea ?

Autorestart

I think that all container should have the flag restart: always, so when the host server reboot the container automatically start.

db:
  build: db
  restart: always
  volumes:
    - ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
    - /etc/localtime:/etc/localtime:ro
  # uncomment the following to enable backup
  #environment:
  #  - AWS_ACCESS_KEY_ID=XXXX
  #  - AWS_SECRET_ACCESS_KEY=XXXX
  #  - WALE_S3_PREFIX=s3://BUCKET_NAME/PATH
  #  - AWS_REGION=us-east-1
app:
  build: app
  restart: always
  links:
    - db:db
  volumes:
    - ./volumes/app/mattermost/config:/mattermost/config:rw
    - ./volumes/app/mattermost/data:/mattermost/data:rw
    - /etc/localtime:/etc/localtime:ro
web:
  build: web
  restart: always
  ports:
    - "80:80"
    - "443:443"
  links:
    - app:app
  volumes:
      # This directory must have cert files
    - ./volumes/web/cert:/cert:ro
    - /etc/localtime:/etc/localtime:ro
  environment:
    - MATTERMOST_ENABLE_SSL=false
    - PLATFORM_PORT_80_TCP_PORT=80

postgres volumes

sorry i'm not pro would like to do the docker install but want to specify my storage volume... how can i do that?

is there a way to add or change system user?

Starting Nginx ln: failed to create symbolic link '/etc/nginx/sites-enabled/mattermost': File exists

can anyone tell me what is causing this?

Android app can't find server

Alpine instead of ubuntu

I believe since Docker official images are moving to alpine instead of ubuntu basically cause the alpine image is a lot smaller than ubuntu we should consider to do the same thing.

What are your thoughts on this?

Big pg_xlog folder

After I use this images and built the container with docker compose, I found out that there are big folder called pg_xlog.

How can I delete that and keep the folder size small forever ?

How would webrtc settings get manifested in the config.template.json file?

I was experimenting a bit with this new feature and wanted to see how I might add the configuration settings defined here directly in the config.template.json file.

Would they be arranged under a WebrtcSettings { } section ... or is this dockerized mattermost not set up to handle these yet? I was also looking under the config file on mattermost-docker-preview, but there's no precedent of how things are handled there either.

I'm using the dockerized webrtc set-up, as defined here.

Thanks.

Kubernetes manifests?

I have converted this to working on Kubernetes and I wasn't sure if you would like to have them in this repo (perhaps in a kubernetes sub folder). If not I can maintain them in my own repo but I thought I should ask before doing work to make them generic configs and submitting a PR.

Bucket name contains invalid characters

Having just upgrade from version 3.2 to version 3.5.1, I'm finding the Wal-E set-up against S3 complaining about bucket name. This wasn't something I was previously aware of.

In the console, I'm getting 500 errors when mattermost tries to get a user's profile image:
http://myserver.com:8001/api/v3/users/65k7nxg67t8uzknbzwtzeiqfnc/image?time=1464276885722

{"id":"api.file.write_file.s3.app_error","message":"Encountered an error writing to S3","detailed_error":"Bucket name contains invalid characters.","request_id":"inifyoqwf7rujykh1umnapuuar","status_code":500}

In the app, the user profile images are failing.

The bucket prefix looks like this:
WALE_S3_PREFIX=s3://mybucket.mattermost/version_3.0

As I've said, I used this in earlier versions without a problem.
Can't see any references to this problem on https://github.com/wal-e/wal-e
Any thoughts on what might be going wrong here?

Add support for corporate proxy environment

Hi all,

I'm trying to run the docker-compose installation and I ran into a small problem,
I was getting 404 errors on the "apt-get update && apt-get install" and I figured it was because of our beloved proxy again.

Adding ENV variables to the Dockerfiles fixed it :

ENV http_proxy <HTTP_PROXY>
ENV https_proxy <HTTPS_PROXY>

Where HTTP_PROXY and HTTPS_PROXY are replaced by the url of the proxy in question.
Any ideas how this could be implemented ? I can dig further and provide a PR if this is OK with you guys.

Ubuntu 16.04 64-bit Issue

My install gets to Step 8 Service 'web' failed to build: lstat cert/cert.pem: no such file or directory. Any hints on what the problem might be?

Using Mattermost Platform CLI on docker install

Please excuse my ignorance because I am quite new to docker but I would like to use the Mattermost command line tools (https://docs.mattermost.com/administration/command-line-tools.html) on an instance of mattermost I have installed with docker-compose. When I try to run platform I am getting command not found. The docs say this must be run from the directory where the Mattermost platform is installed but I am not sure where this would be if installed via Docker. Any help would be appreciated.

Getting Websock error

I am logging the following error with my ElasticBean Mattermost instance on AWS:

websocket connect err: websocket: could not find connection header with token 'upgrade

as far as I can tell there is no nginx configuration and I think I have traced the problem to the instance being automatically setup for load balancing (which AWS service may not support websockets). Is there a tweak to the Dockerrun.aws.json that could override this issue?

Install on Red Hat Enterprise Linux Server release 7.2 (Maipo)

docker : Docker version 1.11.2, build b9f10c9
docker-compose: docker-compose version 1.7.1, build 0a9ab35

After docker-compose up -d

mattermostdocker_db is Exited

And docker start -i mattermostdocker_db_1 give

[docker@localhost mattermost-docker]$ docker start -i mattermostdocker_db_1
AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

initdb: could not access directory "/var/lib/postgresql/data": Permission denied
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

The same error is present on os x installation
os x el capitan : 15.0.0 Darwin Kernel Version 15.0.0
Docker version 1.11.1, build 5604cbe
docker-compose version 1.7.1, build 0a9ab35

Dockfile not updated on team-and-enterprise branch

Line of Code

Installation documentation still suggests using team-and-enterprise branch for production, so it would be nice if Dockfile on that branch get updated to v3.5.1.

Docker versus docker-compose

How difficult would it be to build this without docker-compose? Some detailed instructions would be great.

Pull DB settings from environment variables.

The db settings need to be manually updated at config, make_db, and app/dockerfile. Can these be updated to read from one file / environment variables?

incorrect directory for certificate files?

README.md says:

Put your SSL certificate as ./volumes/cert/cert.pem and the private key that has no password as ./volumes/cert/key-no-password.pem.

docker-compose.yml says:

# This directory must have cert files

./volumes/web/cert

Where is https://hub.docker.com/r/mattermost/webrtc/ Dockerfile?

How to migrate from Mattermost 2.x MySQL to Mattermost 3.x PostgreSQL ?

I have searched in multiple information sources (website, doc, several Github projects) but can't find the way to migrate from 2.x to 3.x, with MySQL as source database :/

Oh, and I use this Docker image for now.

[BUG] Lack of AWS S3/wal-e backup leads to full disks

Hi again guys,

We've been running this instance for a few days now and in this last hour I was struck with a very nice error of database, the db container died out of lack of space in disk. the volumes folder had 53GB 😮 .

Turns out that, if wal-e fails to backup, the postgresql db will start saving various WAL files in a folder called pg_xlog (this was the 53GB monster).

I followed this post to recover everything and restart my mattermost server without any issue 😄

All safe guys!
Since this is planned to use in production, this could be a issue...
Thank you all,
Psidium

Problems with SMTP

Is this container supposed to be able to talk over SMTP ports (25 or 465)? I tried getting this to talk to postfix on the same machine, and also tried sending mail through amazon SES -- neither worked, the SMTP connection failed.

No sign up button

Not sure if this is the appropriate place to post this, but I see no sign up buton, and I have enabled user account creation with:

  "EmailSettings": {
        "EnableSignUpWithEmail": true,
       ....

I know the settings are working because it's picking up my login with gitlab settings (I can see the login with gitlab button) and mailserver settings.

Any ideas?

http to https redirect is not working

at least there is missing ";" in the config.

db container fails to start with chmod error

[gtyler@torgtylervm1 mattermost-docker]$ docker-compose up db
Starting mattermostdocker_db_1
Attaching to mattermostdocker_db_1
db_1   | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1   | chmod: changing permissions of ‘/var/lib/postgresql/data’: Permission denied
mattermostdocker_db_1 exited with code 1

Running on Centos 7 with:

Docker:

Client:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 16:16:33 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 16:16:33 2016
 OS/Arch:      linux/amd64

And docker-compose:

docker-compose version 1.7.1, build 0a9ab35
docker-py version: 1.8.1
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

How to fix `ERROR: for db Container command '/docker-entrypoint1.sh' could not be invoked` on Windows

I thought I'd try out this Docker setup, but after all the images are built, I get this message:

ERROR: for db Container command '/docker-entrypoint1.sh' could not be invoked.

I don't get any debugging messages, but a bit of sleuthing discovered that this is caused by a couple Docker-and-Git-on-Windows issues:

Windows doesn't support the executable bit, and
Windows Git clients are usually set up with autocrlf, which adds a ^M to the end of the #!/bin/bash line in db/docker-entrypoint1.sh.

So, for Windows users I'd recommend the following:

In the repo's directory, run git config core.autocrlf false and checkout the code again (using git reset --hard HEAD or whatever you prefer).
In db/docker-entrypoint1.sh, add the line RUN chmod +x /docker-entrypoint1.sh after the line COPY docker-entrypoint1.sh /.

These two things allowed me to run Mattermost without troubles on Windows!

the https://hub.docker.com/r/mattermost/platform/ image is gone !

Hi,

We are using this image for our production environment.

Can you restore it please ? Or maybe this image should not be used in production ?

Problem spinning up cluster

Greetings!

I'm using docker 1.12 and docker-compose 1.8. When I spin up the cluster, I am getting the following errors in the database docker log (sampling of errors):

ERROR:  relation "systems" does not exist at character 19
STATEMENT:  SELECT Value FROM Systems WHERE Name='Version'
ERROR:  relation "idx_teams_name" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_teams_invite_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_teammembers_team_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_teammembers_user_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channels_team_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channels_name" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channelmembers_channel_id" does not exist
STATEMENT:  SELECT $1::regclass
ERROR:  relation "idx_channelmembers_user_id" does not exist

I get this both by using docker compose and building locally, as well as pulling down the mattermost/mattermost-prod images and manually building run commands.

It appears as though the expected tables do not exist.

For grins, I'm testing on a different host (the one giving the error is on aws) to compare.

Can I run Mattermost on a port other than 80?

I am trying to install Mattermost on a local box so we can do some proof of concept work to see if it is the right fit for us. I am able to install it via docker compose however it is set up to listen on port 80 which is being used by another process on that box. I tried changing - "80:80" to - "8081:80" in the docker-compose.yml which should map 80 to 8081 however when I run docker-composer restart and docker-compose up -d, I can't reach mattermost on localhost:8081. Is there anything I am missing?

Install without TLS certificate

Add mattermost-push-proxy as an optional service in docker-compose.yml

It would be nice if we could have the push notifications service as part of the services setup and managed by docker. At best we would only have to provide it with the location of the public/private keys from Apple as well as the Android API from Google.

Link in README is not up to date

Production-Ubuntu.md doesn't exist anymore

Mattermost 3.5

Hi,
Could you update your Docker images to use the new 3.5 release ?

Thx

mattermost / mattermost-docker Goto Github PK

mattermost-docker's Introduction

Deprecated

mattermost-docker's People

Contributors

Stargazers

Watchers

Forkers

mattermost-docker's Issues

Recommend Projects

Recommend Topics

Recommend Org