Hi Folks,

there is perhaps a wrong tar-File in Line 21 in the Dockerfile.

Line 21:
RUN tar -zxvf ./mattermost-team-3.2.0-linux.amd64.tar.gz

it should be (?):
RUN tar -zxvf ./mattermost-team-3.2.0-linux-amd64.tar.gz

instead of "." an "-"

best regards
Philip

Hi,

Been trying the last few days to run the preview. But it won't reply when accessing the URL.

What steps can I take to check if it's running inside the container and is accessible.

When I attach the shell, I get some errors.
I'll try posting them later. (The disadvantage of using a different platform at work than 1Password and a giant random password for Github :-P)

Ed1t: https://gist.github.com/MindTooth/c0334c4e655db60c23740b61350d3032

Hi!
When i started my container with command:
docker run --name mattermost-preview -d --publish 8065:8065 --add-host dockerhost:127.0.0.1 mattermost/mattermost-preview

i have one error:
Error: failed to load configuration: unable to load on store creation: parsing error at line 109, character 42: json: cannot unmarshal string into Go struct field TeamSettings.TeamSettings.ExperimentalDefaultChannels of type []string

Can you fix docker_config.json at 109 line on this?
"ExperimentalDefaultChannels": []

OS: Debian 10 Buster and WSL 2
Docker version 20.10.0, build 7287ab3

Is there a way to have a docker file that pulls in the latest code from https://github.com/mattermost/platform and build the preview image? This would give a chance to test the latest code with before releases to see how things will change. Loaded with a bunch of the preview posts and users would give a good feel of the changes and explore it fully before live systems. This could make updating the systems quicker as the changes will be familiar in advance.

This what "Preview Image" means to me. :)

Thanks.

how can i build it to deploye on my ARM server

After updating to the latest docker preview image, and running a new container, selecting "Don't have an account?" on the login page does not allow the user to create a new System Admin account. Instead, it links to http://localhost:8065/access_problem, and instructs the user to contact the workspace admin.

I tried to install via AWS Elastic Beanstalk Docker but I'm getting a 502 Bad Gateway error. https://docs.mattermost.com/install/setting-up-aws-elastic-beanstalk-docker.html

Can you please me with this?

Can you try it from your end? maybe I'm making a mistake, maybe not.

Upgrade to mattermost 5.0.0 indicated an error.

mattermost_1 | ------------------------------------ ERROR ------------------------------------------------
mattermost_1 | The platform binary has been deprecated, please switch to using the new mattermost binary.
mattermost_1 | The platform binary will be removed in a future version.
mattermost_1 | -------------------------------------------------------------------------------------------

Hi Team,

Though I could observe port 8065 is in listen state after running one line install

docker run --name mattermost-preview -d --publish 8065:8065 mattermost/mattermost-preview

unable to either telnet or open in broswer.

Please note that 8065 is exposed to outside and also telnet fails when tried with localhost.

Same like in the closed issue #40:

2019-03-09T13:10:30.684278Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-03-09T13:10:30.687302Z 0 [Note] Event Scheduler: Loaded 0 events
2019-03-09T13:10:30.687587Z 0 [Note] mysqld: ready for connections.
Version: '5.7.25'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
Updating CA certificates
Starting platform
./docker-entry.sh: line 18: /mm/mattermost/bin/mattermost: No such file or directory

helge@Zini18 ~ $ docker images
REPOSITORY                      TAG                 IMAGE ID            CREATED             SIZE
mattermost/mattermost-preview   latest              d4a54b3ce221        41 hours ago        560MB

Was just trying the one-line install from https://mattermost.com/download/ This is on macOS 10.14.

If I add --add-host dockerhost:127.0.0.1 as suggested in the install, same error:

2019-03-09T13:17:17.360524Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-03-09T13:17:17.363559Z 0 [Note] Event Scheduler: Loaded 0 events
2019-03-09T13:17:17.363817Z 0 [Note] mysqld: ready for connections.
Version: '5.7.25'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
Updating CA certificates
./docker-entry.sh: line 18: /mm/mattermost/bin/mattermost: No such file or directory
Starting platform

helge@Zini18 ~ $ docker ps -a
CONTAINER ID        IMAGE                           COMMAND                  CREATED              STATUS                            PORTS               NAMES
37c44bc6b89c        mattermost/mattermost-preview   "/bin/sh -c ./docker…"   About a minute ago   Exited (127) About a minute ago                       mattermost-preview

I know this is a minor issue but the Dockerfile has a copyright notice and says to reference License.txt, which doesn't exist in this repo. I'm customizing the Dockerfile so that would be handy.

Hi,

everytime one refreshes his Browser, he gets the Login Screen and is logged out.

What could be the reason? Maybe related to Cookies?

We use a Reverse Proxy (Apache) and this is the Config:

  ProxyPreserveHost On

  # setup the proxy
  <Proxy *>
         Order allow,deny
         Allow from all
  </Proxy>

  # Set web sockets
  RewriteEngine On
  RewriteCond %{REQUEST_URI} /api/v[0-9]+/(users/)?websocket [NC,OR]
  RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR]
  RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC]
  RewriteRule .* ws://127.0.0.1:8065%{REQUEST_URI} [P,QSA,L]
  RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f


  <LocationMatch "^/api/v(?<apiversion>[0-9]+)/(?<apiusers>users/)?websocket">
        Require all granted
        ProxyPass ws://127.0.0.1:8065/api/v%{env:MATCH_APIVERSION}/%{env:MATCH_APIUSERS}websocket
        ProxyPassReverse ws://127.0.0.1:8065/api/v%{env:MATCH_APIVERSION}/%{env:MATCH_APIUSERS}websocket
        ProxyPassReverseCookieDomain 127.0.0.1 mattermost.example.com
  </LocationMatch>

  <Location />
        Require all granted

  </Location>

        ProxyPass /.well-known !
        ProxyPass / http://127.0.0.1:8065/
        ProxyPassReverse / http://127.0.0.1:8065/
        ProxyPassReverseCookieDomain 127.0.0.1 mattermost.example.com

To reproduce.

1. Configure the GitLab / Mattermost slash commands integration
2. Try a slash command (e.g. /my-repo help)

You will find the error message in the container console log file
x509: failed to load system roots and no roots provided

This is because the ca-certificates package has not been included in the container build so the mattermost process cannot verify the GitLab website via SSL (no certs to compare to).

As a workaround, I opened a shell to the running container and issued the following commands:

apt-get update
apt-get install ca-certificates

After restarting the container instance, the error/message should be eliminated from the console log.

Mattermost Version: 5.2.1
Database Schema Version: 5.2.0
Database: mysql

Getting the below error.

==

------------------------------------ ERROR ------------------------------------------------

The platform binary has been deprecated, please switch to using the new mattermost binary.

The platform binary will be removed in a future version.

{"level":"error","ts":1565703136.6825554,"caller":"commands/server.go:74","msg":"The platform binary has been deprecated, please switch to using the mattermost binary."}

{"level":"error","ts":1565703137.3925903,"caller":"plugin/client_rpc.go:154","msg":"RPC call to OnActivate plugin failed.","plugin_id":"zoom","error":"reading body EOF"}

{"level":"error","ts":1565703137.4114516,"caller":"plugin/client_rpc_generated.go:66","msg":"RPC call OnConfigurationChange to plugin failed.","plugin_id":"zoom","error":"connection is shut down"}

{"level":"error","ts":1565703137.4423308,"caller":"plugin/client_rpc_generated.go:66","msg":"RPC call OnConfigurationChange to plugin failed.","plugin_id":"zoom","error":"connection is shut down"}

Could anyone help?

Any chance you could add an environment variable to make the mysql startup optional?

Hi mattermost team!

I tried to deploy this preview image on top of k8spin. K8Spin runs every workload using gVisor to isolate workloads.

This container image does not work. Seems like the Dockerfile contains an "invalid" VOLUME definition (relative path instead of absolute ones).

  Warning  Failed     6s    kubelet, gke-k8spin-live-k8spin-clients-5ee92b0f-8m4s  Error: failed to create containerd task: OCI runtime create failed: /home/containerd/usr/local/sbin/runsc did not terminate sucessfully: reading spec: Mount.Destination must be an absolute path: &{./mattermost-data bind /var/lib/containerd/io.containerd.grpc.v1.cri/containers/mattermost/volumes/98359f54ac8f3a1026735d87f217154c46dd2d71e6eb5e4ffc2187583277d2db [rbind rprivate rw]}

Looking for the error on internet i found: https://sourcegraph.com/github.com/google/gvisor/-/blob/runsc/specutils/fs.go#L112

So, changing the VOLUME definition should be enough to run this image in a gVisor pod on top of kubernetes

I will test the solution before open a PR @cpanato!

Thanks!

Using the latest docker image it exits during startup:

$ docker ps -a
CONTAINER ID        IMAGE                           COMMAND                  CREATED             STATUS                     PORTS               NAMES
2c9af14551b5        mattermost/mattermost-preview   "/bin/sh -c ./docker-"   2 minutes ago       Exited (0) 2 minutes ago                       mattermost-preview

I've successfully used the preview image in the past. It looks like this started happening on January 5th.

Hi,

I cannot share a file with another user.

Everything seems to work correctly, however the user does not see the shared file.

Do you know why?

Regards,
Alain

After starting up this preview image for the first time via the one-liner documented here I'm trapped at the sign in page. There's no default user account documented, and I'm not given the option to generate the initial admin account.

EDIT:

After investigating this further I was able to proceed by editing the config file like so:

First:

docker exec -ti mattermost-preview /bin/bash
apt install vim
vim mattermost/config/docker_config.json

Then:

Set EnableOpenServer to true

docker restart mattermost-preview

After that I was able to generate myself an account.

Since this is designed to be a quick preview of mattermost I think it would be a good idea if that setting was turned on by default so that it's quicker to dive into

Currently,

data volume in Dockerfile is /mm/mattermost-data
data folder in config_docker.json is /mm/mattermost/mattermost-data

It should to be a same path.

Unable to start Mattermost 4.10.4 because renaming from ./bin/platform to ./bin/mattermost was made at 5.0.

$ docker run --publish 8065:8065 -it mattermost/mattermost-preview:4.10.4 | tail
2018-10-19T23:40:56.012209Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-10-19T23:40:56.012234Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-10-19T23:40:56.012265Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2018-10-19T23:40:56.014576Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2018-10-19T23:40:56.014726Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2018-10-19T23:40:56.020072Z 0 [Note] Event Scheduler: Loaded 0 events
2018-10-19T23:40:56.020286Z 0 [Note] mysqld: ready for connections.
Version: '5.7.23'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
Starting platform
./docker-entry.sh: line 15: /mm/mattermost/bin/mattermost: No such file or directory

Why is 4.0 tagged as latest instead of 4.1?

I tried the Local Machine Setup using Docker but the service didn't come up. Opening a shell into the container and running ./bin/platform --config=config/config_docker.json as done in the docker-entry.sh shows the following error:

Failed to ping DB retrying in 10 seconds err=dial tcp: lookup dockerhost on 192.168.65.1:53: no such host

I wasn't able to find out which part of the setup tries to resolve dockerhost and how to change that. Same result when running in Docker on Mac OS X and Ubuntu 16.

Output of docker version:

Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:47:50 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:47:50 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 3
 Running: 1
 Paused: 0
 Stopped: 2
Images: 2
Server Version: 1.11.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 33
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge null host
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.767 GiB
Name: warmachine
ID: REDACTED
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Steps to reproduce the issue:

1. docker run --name mattermost-preview -d --publish 8065:8065 mattermost/mattermost-preview

Describe the results you received:
I cannot access the 8065 port via localhost.

curl localhost:8065
curl: (56) Recv failure: Connection reset by peer

Describe the results you expected:
localhost:8065 should be accessible via browser.

Additional information you deem important (e.g. issue happens only occasionally):
docker inspect mattermost-preview
https://gist.github.com/0006mathew/921e560e6ce1f13d8fded53535912ec6

[2017/01/13 01:32:31 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:32:31 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=34wjguqehbyw7jakqawwxhxh7e uid= ip=192.168.10.228 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:34:17 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:34:17 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=cn7nwksc9fyh5g7kif5b5be18e uid= ip=192.168.10.228 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:36:34 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:36:34 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=5eyafyffz7dm7g6kf774p9bzww uid= ip=192.168.10.228 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:37:16 UTC] [EROR] /hooks/gi9qtkpsub8t7y1qffzinssmyh:incomingWebhook code=500 rid=6xk43z7as3yopxn1a6gkdzj7ur uid= ip=10.0.0.2 Invalid webhook [details: err=store.sql_webhooks.get_incoming.app_error]
[2017/01/13 01:37:31 UTC] [EROR] /hooks/gi9qtkpsub8t7y1qffzinssmyh:incomingWebhook code=500 rid=4pmu4qi3j3ruijzumpfeq8wa3r uid= ip=10.0.0.2 Invalid webhook [details: err=store.sql_webhooks.get_incoming.app_error]
[2017/01/13 01:38:38 UTC] [EROR] /hooks/gi9qtkpsub8t7y1qffzinssmyh:incomingWebhook code=500 rid=bigtmseqhbnydjm5337wbsk4py uid= ip=10.0.0.2 Invalid webhook [details: err=store.sql_webhooks.get_incoming.app_error]
[2017/01/13 01:39:17 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:39:17 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=f16hqf7oopg35kxukefoutcj4e uid= ip=192.168.10.228 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:15 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:15 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=ixye8c7jetbkxck6mowh5ifenw uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:19 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:19 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=xw6p98afq3rmp86ib715cp1uzw uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:22 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:22 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=7ehxnnjmcbgezrichsaeqshxyw uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:25 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:25 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=ukpkndrmcfnkjg3iiwy7enckwe uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:28 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:28 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=34fga1iw3bbg3ekhncq5pcq5qh uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:31 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:31 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=9rr571tzxby8jre15a56d51xny uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:34 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:34 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=4mw8zyhz97nabpifqihebyot5w uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:35 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:35 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=8gs5rd4ydp8hmbfiy6tacwqoje uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:38 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:38 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=3yq1trxum3g7tkkerbxsu8u1qh uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:38 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:38 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=xtryno1futra3ci1awn9iuydtr uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:41 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:41 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=ngohzb6u9bd1xkgtwjmbyjoujy uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:44 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:44 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=31c9pdhfopd6fbygimtbpx6kce uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:47 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:47 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=c83w59g55tno7jsr7konh8ztyr uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:50 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:50 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=5qppp1896b8uxmrnofu73jja1o uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:53 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:53 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=y1bpp1wdwjy4xcoymy4gxiscbe uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:40:57 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:40:57 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=phy49ap9c7ffxkrcc393xhfnkw uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:41:35 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:41:35 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=e1unzmxc4ibafp8jfiezyspfwr uid= ip=192.168.10.228 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:43:51 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:43:51 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=84j7ejq9f7g9f8paoh3wukcrzo uid=yiik4coa83ffpm9e1yjohjrf1r ip=192.168.10.212 Failed to upgrade websocket connection [details: ]
[2017/01/13 01:44:17 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2017/01/13 01:44:17 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=n4jjrn4stjfhdyujppdj3k7tge uid= ip=192.168.10.228 Failed to upgrade websocket connection [details: ]