zammad / zammad-docker-compose Goto Github PK

Zammad Docker images for docker-compose

Home Page: https://hub.docker.com/r/zammad/zammad-docker-compose/

License: GNU Affero General Public License v3.0

zammad-docker-compose's Introduction

Welcome to Zammad

Zammad is a web based open source helpdesk/ticket system with many features to manage customer communication via several channels like telephone, facebook, twitter, chat and emails. It is distributed under the GNU AFFERO General Public License (AGPL). Do you receive many emails and want to answer them with a team of agents? You're going to love Zammad!

Use cases

This repository is the starting point if you want to:

deploy Zammad in a containerized production environment
test the current stable or develop versions of Zammad

Getting started

Learn more on Zammad’s documentation

Upgrading

For upgrading instructions see our Releases.

Status

Using a reverse proxy

In environments with more then one web applications it is necessary to use a reverse proxy to route connections to port 80 and 443 to the right application. To run Zammad behind a reverse proxy, we provide docker-compose.proxy-example.yml as a starting point.

Copy ./.examples/proxy/docker-compose.proxy-example.yml to your own configuration, e.g. ./docker-compose.prod.yml cp ./.examples/proxy/docker-compose.proxy-example.yml ./docker-compose.prod.yml
Modify the environment variable VIRTUAL_HOST and the name of the external network in ./docker-compose.prod.yml to fit your environment.
Run docker-composer commands with the default and your configuration, e.g. docker-compose -f docker-compose.yml -f docker-compose.prod.yml up -d

See .examples/proxy/docker-compose.yml for an example proxy project.

Like this, you can add your docker-compose.prod.yml to a branch of your Git repository and stay up to date by merging changes to your branch.

Using Rancher

RANCHER_URL=http://RANCHER_HOST:8080 rancher-compose --env-file=.env up

Running without Elasticsearch

Elasticsearch is an optional, but strongly recommended dependency for Zammad. More details can be found in the documentation. There are however certain scenarios when running without Elasticsearch may be desired, e.g. for very small teams, for teams with limited budget or as a temporary solution for an unplanned Elasticsearch downtime or planned cluster upgrade.

Elasticsearch is enabled by default in the example docker-compose.yml file. It is also by default required to run the "zammad-init" command. Disabling Elasticsearch is possible by setting a special environment variable: ELASTICSEARCH_ENABLED=false for the zammad-init container and removing all references to Elasticsearch everywhere else: the zammad-elasticsearch container, its volume and links to it.

zammad-docker-compose's People

Contributors

Stargazers

Watchers

Forkers

monotek remlabm samjaninf teefax prohealthbox mcbridet nomaster ffddorf t3easy sysbind dobrud beyond-agentur moifort www3838438 muhammadn mirroam andrevandal mainwebsolutions kgw4it union-software-cooperative pauradev adammcmaster bespaloff b4rti jannikzed rocklau diproart botux equero loggencocka jan-moxter code-samurai farooqarahim jzjad domehuhu namanyahillary cloudstek abeluck wbonis simplificator fuzhanli liquibrium fxcebx fookatchu alfatraining rlue lobonerd dan-pcces michaelsimon101 ananthrajtag donbowman m-hume netgurru shokinn wende glitchwraith it-globcoin redaranj iwanhusnawan 4talent rene-ww gilbertsoft teawithfruit wushian ylascombe amauryfv nicolasmgaray thiagoalcav alitheg drbw dsaht cubyte-oss xtruthx mircoblitz lumpov rennefeld narendrapsgim kibosj xrstf cristianvirtual dafttt digitalorganic andradelisandro maaz90-mx luisriverag pc-ego xroi0x61 netengine-at vzankov rosscdh hashwagon fstaske xxpqxx fhuu geosiga colpari anh2kjnhbac2009 kobeumut tbertrand-eef enoch85

zammad-docker-compose's Issues

Use zammad version as image tags

Expected behavior:

I want to run a Zammad docker-compose environment with a defined stable version of zammad e.g. "2.1.1".

Actual behavior:

There's no way of achieving this with docker image tags as they are not versioned according to the Zammad releases. There are version tags like -79 but I can't find any explanation which version that would match. As an administrator I'd like to decide which exact version to use and when I would like to upgrade just increase the version tag of the image, test it and update my environment.

sysctl -w vm.max_map_count=262144

Hi,

I use docker in plesk to install but i receive this error:
sysctl -w vm.max_map_count=262144 can not be set in container, there is File in read only?

I have set up in host system sysctl -w vm.max_map_count=262144 but don't work?

Backup container using Debian based image

zammad-backup is using an image based on the Debian image and installing postgresql into it.

Is there a reason not using the zammad-postgresql image I'm overseeing? It also has the pg_dump command and using this will save resources in many places (diskspace, travis-ci, time and data pulling the images ...).

Thanks for doing such a great work, Jan.

Zammad image layers are not optimal

Infos:

Docker version: 17.06
Docker-compose version: 0.12.1
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

Small image size

Actual behavior:

Install and uninstall in different steps generates larger image because of the layers

Lost File Storage during container Crash - What can I DO?

Hey guys, having some trouble with Zammad Docker-Compose version in rancher.

I've tried to create custom fields in Object ticket, and some error ocurred, I couldn't catch the log, but I tried then to restart the railsserver container and the role server stopped, so I reinitiated the server and everything comes up again, but railsserver is failing to start, here is the log output:

13/05/2017 15:24:35railsserver can access postgresql server now...
13/05/2017 15:24:39/home/zammad/app/models/store/provider/file.rb:32:in `get': ERROR: No such file /home/zammad/storage/fs/46f4/bbc1/1a20c/98d79/cbd1356/8769d0b/7a9a88643f12eb5c96b68d75a5c55371 (RuntimeError)
13/05/2017 15:24:39	from /home/zammad/app/models/store/file.rb:62:in `content'
13/05/2017 15:24:39	from /home/zammad/app/models/store.rb:147:in `content'
13/05/2017 15:24:39	from /home/zammad/lib/static_assets.rb:141:in `filename'
13/05/2017 15:24:39	from /home/zammad/lib/static_assets.rb:126:in `read'
13/05/2017 15:24:39	from /home/zammad/lib/static_assets.rb:164:in `sync'
13/05/2017 15:24:39	from /home/zammad/config/initializers/logo.rb:4:in `<top (required)>'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `block in load'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:652:in `block in load_config_initializer'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:651:in `load_config_initializer'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `each'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `block in <class:Engine>'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `instance_exec'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `run'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:55:in `block in run_initializers'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `each'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `tsort_each_child'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:415:in `call'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:415:in `each_strongly_connected_component_from'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:347:in `each'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:347:in `call'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
13/05/2017 15:24:39	from /usr/local/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:54:in `run_initializers'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:352:in `initialize!'
13/05/2017 15:24:39	from /home/zammad/config/environment.rb:5:in `<top (required)>'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `block in require'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:39	from /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:328:in `require_environment!'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/commands/runner.rb:52:in `<top (required)>'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/commands/commands_tasks.rb:123:in `require'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/commands/commands_tasks.rb:123:in `require_command!'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/commands/commands_tasks.rb:90:in `runner'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
13/05/2017 15:24:39	from /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/commands.rb:17:in `<top (required)>'
13/05/2017 15:24:39	from bin/rails:4:in `require'
13/05/2017 15:24:39	from bin/rails:4:in `<main>'
13/05/2017 15:24:43creating db & searchindex...
13/05/2017 15:24:46zammad_production already exists
13/05/2017 15:24:50rake aborted!
13/05/2017 15:24:50ERROR: No such file /home/zammad/storage/fs/46f4/bbc1/1a20c/98d79/cbd1356/8769d0b/7a9a88643f12eb5c96b68d75a5c55371
13/05/2017 15:24:50/home/zammad/app/models/store/provider/file.rb:32:in `get'
13/05/2017 15:24:50/home/zammad/app/models/store/file.rb:62:in `content'
13/05/2017 15:24:50/home/zammad/app/models/store.rb:147:in `content'
13/05/2017 15:24:50/home/zammad/lib/static_assets.rb:141:in `filename'
13/05/2017 15:24:50/home/zammad/lib/static_assets.rb:126:in `read'
13/05/2017 15:24:50/home/zammad/lib/static_assets.rb:164:in `sync'
13/05/2017 15:24:50/home/zammad/config/initializers/logo.rb:4:in `<top (required)>'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `block in load'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:652:in `block in load_config_initializer'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:651:in `load_config_initializer'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `each'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `block in <class:Engine>'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `instance_exec'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `run'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:55:in `block in run_initializers'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `each'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `tsort_each_child'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:54:in `run_initializers'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:352:in `initialize!'
13/05/2017 15:24:50/home/zammad/config/environment.rb:5:in `<top (required)>'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `block in require'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:50/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:328:in `require_environment!'
13/05/2017 15:24:50/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:457:in `block in run_tasks_blocks'
13/05/2017 15:24:50/usr/local/bundle/gems/rake-11.2.2/exe/rake:27:in `<top (required)>'
13/05/2017 15:24:50/usr/local/bin/bundle:22:in `load'
13/05/2017 15:24:50/usr/local/bin/bundle:22:in `<main>'
13/05/2017 15:24:50Tasks: TOP => db:migrate => environment
13/05/2017 15:24:50(See full trace by running task with --trace)
13/05/2017 15:24:53rake aborted!
13/05/2017 15:24:53ERROR: No such file /home/zammad/storage/fs/46f4/bbc1/1a20c/98d79/cbd1356/8769d0b/7a9a88643f12eb5c96b68d75a5c55371
13/05/2017 15:24:53/home/zammad/app/models/store/provider/file.rb:32:in `get'
13/05/2017 15:24:53/home/zammad/app/models/store/file.rb:62:in `content'
13/05/2017 15:24:53/home/zammad/app/models/store.rb:147:in `content'
13/05/2017 15:24:53/home/zammad/lib/static_assets.rb:141:in `filename'
13/05/2017 15:24:53/home/zammad/lib/static_assets.rb:126:in `read'
13/05/2017 15:24:53/home/zammad/lib/static_assets.rb:164:in `sync'
13/05/2017 15:24:53/home/zammad/config/initializers/logo.rb:4:in `<top (required)>'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `block in load'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:652:in `block in load_config_initializer'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:651:in `load_config_initializer'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `each'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `block in <class:Engine>'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `instance_exec'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `run'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:55:in `block in run_initializers'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `each'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `tsort_each_child'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:54:in `run_initializers'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:352:in `initialize!'
13/05/2017 15:24:53/home/zammad/config/environment.rb:5:in `<top (required)>'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `block in require'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:53/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:328:in `require_environment!'
13/05/2017 15:24:53/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:457:in `block in run_tasks_blocks'
13/05/2017 15:24:53/usr/local/bundle/gems/activerecord-4.2.7.1/lib/active_record/railties/databases.rake:182:in `block (2 levels) in <top (required)>'
13/05/2017 15:24:53/usr/local/bundle/gems/rake-11.2.2/exe/rake:27:in `<top (required)>'
13/05/2017 15:24:53/usr/local/bin/bundle:22:in `load'
13/05/2017 15:24:53/usr/local/bin/bundle:22:in `<main>'
13/05/2017 15:24:53Tasks: TOP => db:abort_if_pending_migrations => environment
13/05/2017 15:24:53(See full trace by running task with --trace)
13/05/2017 15:24:57rake aborted!
13/05/2017 15:24:57ERROR: No such file /home/zammad/storage/fs/46f4/bbc1/1a20c/98d79/cbd1356/8769d0b/7a9a88643f12eb5c96b68d75a5c55371
13/05/2017 15:24:57/home/zammad/app/models/store/provider/file.rb:32:in `get'
13/05/2017 15:24:57/home/zammad/app/models/store/file.rb:62:in `content'
13/05/2017 15:24:57/home/zammad/app/models/store.rb:147:in `content'
13/05/2017 15:24:57/home/zammad/lib/static_assets.rb:141:in `filename'
13/05/2017 15:24:57/home/zammad/lib/static_assets.rb:126:in `read'
13/05/2017 15:24:57/home/zammad/lib/static_assets.rb:164:in `sync'
13/05/2017 15:24:57/home/zammad/config/initializers/logo.rb:4:in `<top (required)>'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `block in load'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:652:in `block in load_config_initializer'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:651:in `load_config_initializer'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `each'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `block in <class:Engine>'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `instance_exec'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `run'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:55:in `block in run_initializers'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `each'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `tsort_each_child'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:54:in `run_initializers'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:352:in `initialize!'
13/05/2017 15:24:57/home/zammad/config/environment.rb:5:in `<top (required)>'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `block in require'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:24:57/usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:274:in `require'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:328:in `require_environment!'
13/05/2017 15:24:57/usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:457:in `block in run_tasks_blocks'
13/05/2017 15:24:57/usr/local/bundle/gems/rake-11.2.2/exe/rake:27:in `<top (required)>'
13/05/2017 15:24:57/usr/local/bin/bundle:22:in `load'
13/05/2017 15:24:57/usr/local/bin/bundle:22:in `<main>'
13/05/2017 15:24:57Tasks: TOP => searchindex:rebuild => environment
13/05/2017 15:24:57(See full trace by running task with --trace)
13/05/2017 15:24:57starting zammad...
13/05/2017 15:24:57zammad will be accessable on http://localhost in some seconds
13/05/2017 15:24:58Puma starting in single mode...
13/05/2017 15:24:58* Version 3.6.0 (ruby 2.3.1-p112), codename: Sleepy Sunday Serenity
13/05/2017 15:24:58* Min threads: 5, max threads: 30
13/05/2017 15:24:58* Environment: production
13/05/2017 15:25:01! Unable to load application: RuntimeError: ERROR: No such file /home/zammad/storage/fs/46f4/bbc1/1a20c/98d79/cbd1356/8769d0b/7a9a88643f12eb5c96b68d75a5c55371
13/05/2017 15:25:01bundler: failed to load command: puma (/usr/local/bundle/bin/puma)
13/05/2017 15:25:01RuntimeError: ERROR: No such file /home/zammad/storage/fs/46f4/bbc1/1a20c/98d79/cbd1356/8769d0b/7a9a88643f12eb5c96b68d75a5c55371
13/05/2017 15:25:01  /home/zammad/app/models/store/provider/file.rb:32:in `get'
13/05/2017 15:25:01  /home/zammad/app/models/store/file.rb:62:in `content'
13/05/2017 15:25:01  /home/zammad/app/models/store.rb:147:in `content'
13/05/2017 15:25:01  /home/zammad/lib/static_assets.rb:141:in `filename'
13/05/2017 15:25:01  /home/zammad/lib/static_assets.rb:126:in `read'
13/05/2017 15:25:01  /home/zammad/lib/static_assets.rb:164:in `sync'
13/05/2017 15:25:01  /home/zammad/config/initializers/logo.rb:4:in `<top (required)>'
13/05/2017 15:25:01  /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:25:01  /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `block in load'
13/05/2017 15:25:01  /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:240:in `load_dependency'
13/05/2017 15:25:01  /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/dependencies.rb:268:in `load'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:652:in `block in load_config_initializer'
13/05/2017 15:25:01  /usr/local/bundle/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:166:in `instrument'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:651:in `load_config_initializer'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:616:in `block (2 levels) in <class:Engine>'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `each'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/engine.rb:615:in `block in <class:Engine>'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `instance_exec'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:30:in `run'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:55:in `block in run_initializers'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `each'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:44:in `tsort_each_child'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:415:in `call'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:415:in `each_strongly_connected_component_from'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:347:in `each'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:347:in `call'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
13/05/2017 15:25:01  /usr/local/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/initializable.rb:54:in `run_initializers'
13/05/2017 15:25:01  /usr/local/bundle/gems/railties-4.2.7.1/lib/rails/application.rb:352:in `initialize!'
13/05/2017 15:25:01  /home/zammad/config/environment.rb:5:in `<top (required)>'
13/05/2017 15:25:01  config.ru:3:in `require'
13/05/2017 15:25:01  config.ru:3:in `block in <main>'
13/05/2017 15:25:01  /usr/local/bundle/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
13/05/2017 15:25:01  /usr/local/bundle/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
13/05/2017 15:25:01  config.ru:in `new'
13/05/2017 15:25:01  config.ru:in `<main>'
13/05/2017 15:25:01  /usr/local/bundle/gems/rack-1.6.4/lib/rack/builder.rb:49:in `eval'
13/05/2017 15:25:01  /usr/local/bundle/gems/rack-1.6.4/lib/rack/builder.rb:49:in `new_from_string'
13/05/2017 15:25:01  /usr/local/bundle/gems/rack-1.6.4/lib/rack/builder.rb:40:in `parse_file'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/lib/puma/configuration.rb:315:in `load_rackup'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/lib/puma/configuration.rb:243:in `app'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/lib/puma/runner.rb:127:in `load_and_bind'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/lib/puma/single.rb:85:in `run'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/lib/puma/launcher.rb:172:in `run'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/lib/puma/cli.rb:74:in `run'
13/05/2017 15:25:01  /usr/local/bundle/gems/puma-3.6.0/bin/puma:10:in `<top (required)>'
13/05/2017 15:25:01  /usr/local/bundle/bin/puma:17:in `load'
13/05/2017 15:25:01  /usr/local/bundle/bin/puma:17:in `<top (required)>'

after those logs, railsserver container just stops.. Any Ideas?
I still have a postgresql zammad_production sql DUMP to restore. But it seems that it loosed some files stored in the container. There's any way to get my instance working back again?

make zammad nginx work with proxy contaienr

Infos:

Docker version: 17.04.0-ce
Docker-compose version: 1.11.2
Operating system (Docker host): centOS

Expected behavior:

I publish port only on localhost to allow https://github.com/jwilder/nginx-proxy to reverse proxy to it based on environment variables.

Actual behavior:

I get 503 error, nginx-proxy doesn't understand what to do with it.

Steps to reproduce the behavior:

run zammad with jwilder/nginx-proxy in front.

I've also created issue at jwilder/nginx-proxy repo, but we cannot get to the bottom: nginx-proxy/nginx-proxy#793 without your help.

Websocket failed with rancher and rancher lb

Infos:

Docker version: 17.04
Operating system (Docker host): Rancher OS
Orchestrator: Rancher cattle
Rancher version: 1.5.5
Docker volume driver: rancher-nfs
Rancher load balancer version : v0.6.4

Expected behavior:

Real time with chat

Actual behavior:

Chat enabled, but real time don't work, refresh page is necessary to display message...
The websocket does not seem to work

Steps to reproduce the behavior:

Use rancher-composer.yml and docker-compose.yml to load stack on rancher with configure rancher-nfs as volume driver
Create loadbalancer service to provide HTTPS traffic with valid certificate to zammad-nginx on port 80

Possible problem

Load balancer don't support websocket ?
HA Proxy has bad configuration to websocket ?

Environment variables to connect to existing postgres and elasticsearch

We would like to use existing Postgres database and Elasticsearch cluster. Was wondering if I could export the connection and authentication details as docker variables and be able to connect to them?

Any other ways to make this work?

Issue w/ auto deploy in Rancher (may exist with docker-compose as well)

Infos:

Docker version:17.03.1-ce
Docker-compose version: Rancher 1.5.5 (builtin composer?)
Operating system (Docker host): Debian 8

Expected behavior:

Zammad installed from the catalogs should start

Actual behavior:

Install shows all services green, however the railsserver is stalled "Waiting for postgresql server"

Steps to reproduce the behavior:

Install from the catalogue

I have installed Zammad 1.2 from the Rancher catalogues, and it hangs after install. All containers show green, however it always has a 502 gateway failure. After some investigation i found the railsserver container was sitting at waiting for postgresql. upon looking at the Dockerfile, I noticed it waits for a server at service link "zammad-postgresql" when the actual link name is "postgresql". I tried doing a service upgrade and renamed the link to "zammad-postgresql", and it fired right up.

Question: Change port?

Hello,

I try to install this in a container, how can i change the port (for outside)?

railsserver container not starting

Infos:

Docker version: 17.06.2-ce
Docker-compose version: 1.15.0
Operating system (Docker host): Debian 8.9

Expected behavior:

Starting the Rails container.

Actual behavior:

zammad-railsserver_1 | Bundler::RubyVersionMismatch: Your Ruby version is 2.4.1, but your Gemfile specified 2.3.1
zammad-railsserver_1 | /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/definition.rb:486:in validate_ruby!' zammad-railsserver_1 | /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/definition.rb:461:in validate_runtime!'
zammad-railsserver_1 | /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler.rb:95:in setup' zammad-railsserver_1 | /usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.4/lib/bundler/setup.rb:19:in <top (required)>'
zammad-railsserver_1 | /usr/local/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require' zammad-railsserver_1 | /usr/local/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require'

Steps to reproduce the behavior:

docker-compose pull && docker-compose up

Looks like this issue is related to 89473cc

Backup script has path issues

Infos:

Docker version: Docker version 17.05.0-ce, build 89658be
Operating system (Docker host): Linux zammad 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux

Expected behavior:

Backup is created in /var/tmp/zammad_backup/

Actual behavior:

Backup script fails to execute because of hardcoded paths that don't exist

zammad@820f33d582db:~$ /home/zammad/contrib/backup/zammad_backup.sh
/home/zammad/contrib/backup/zammad_backup.sh: line 9: /opt/zammad/contrib/backup/config: No such file or directory
/home/zammad/contrib/backup/zammad_backup.sh: line 12: /opt/zammad/contrib/backup/functions: No such file or directory
/home/zammad/contrib/backup/zammad_backup.sh: line 15: check_database_config_exists: command not found
/home/zammad/contrib/backup/zammad_backup.sh: line 17: delete_old_backups: command not found
/home/zammad/contrib/backup/zammad_backup.sh: line 19: get_backup_date: command not found
/home/zammad/contrib/backup/zammad_backup.sh: line 21: backup_dir_create: command not found
/home/zammad/contrib/backup/zammad_backup.sh: line 23: backup_files: command not found
/home/zammad/contrib/backup/zammad_backup.sh: line 25: backup_db: command not found

caused by the following lines in zammad_backup.sh

# import config
. /opt/zammad/contrib/backup/config

# import functions
. /opt/zammad/contrib/backup/functions

Now you can be smart and work around this issue by creating a symlink using

ln -s /home/zammad /opt/zammad

but while you're still busy enjoying your own cleverness you will try running the backup script again and will get to the next bunch of errors.

zammad@820f33d582db:/$ /home/zammad/contrib/backup/zammad_backup.sh
find: `/var/tmp/zammad_backup/*_zammad_*.gz': No such file or directory
tar: Removing leading `/' from member names
su: must be run from a terminal
mv: cannot stat '/tmp/20170620133837_zammad_db.psql.gz': No such file or directory

So to make it short - the backup script does not work in the containerized version.

Steps to reproduce the behavior:

launch the zammad docker setup, using the images from the compose repo
enter the container zammad-railsserver using docker exec -it zammad-railsserver bash
execute /home/zammad/contrib/backup/zammad_backup.sh

Websocket tmp files

Infos:

Docker version: 17.0.3.1-ce
Docker-compose version: 1.11.2
Operating system (Docker host): Debian Jessie

Expected behavior:

Zammad should clean up tmp files in /home/zammad/tmp/websocket_production/

Actual behavior:

Zammad was running for a couple of weeks without problems, then the system was running out of inodes, and I discovered a lot (1,5 million) of tmp files in /volume/container/location/home/zammad/tmp/websocket_production/

Missing volume link in zammad-railsserver

Infos:

Docker version: 1.10.1
Docker-compose version: Deployed by rancher
Operating system (Docker host): Ubuntu 14

Expected behavior:

Uploaded of images for logo should be visible in login screen

Actual behavior:

There is a broken image link.

Reason is probably because the uploaded image is not stored into the shared data-zammad volume. The zammad-railsserver has no volume reference like:

zammad-railsserver:
    image: zammad/zammad-docker-compose:zammad-railsserver
    labels:
      io.rancher.container.pull_image: always
    links:
      - zammad-elasticsearch
      - zammad-postgresql
    depends_on:
      - zammad
    restart: always
    volumes:
      - data-zammad:/home/zammad

This uploads the image into the container but the zammad-nginx container is not able to access it.

Add kubernetes example

Since kubernetes/ docker swarm became much more popular lately I find it very useful to have an easy option to deploy zammad to my kubernetes cluster.

Is there anyone using kubernetes here besides me?

Elasticsearch configuration is not configured automatically and not documented

Infos:

Docker version: 17.06
Docker-compose version: 0.12.1
Operating system (Docker host): Ubunto 16.04

Expected behavior:

Elasticsearch up and running after initial up

Actual behavior:

Elasticsearch has to be configured manually and there is no hint in the docker-compose documentation part

Steps to reproduce the behavior:

docker-compose up -d
configure new system
open stats
get error message elasticsearch not configured

postgresql-error

Hi,
When I run "docker-compose up" it represents below error:

docker-compose(master)> docker-compose up
Pulling postgresql (zammad/zammad-docker-compose:postgresql)...
ERROR: manifest for zammad/zammad-docker-compose:postgresql not found

The same error even running "docker-compose pull"

Details:
docker-compose(master)> docker --version
Docker version 17.03.1-ce, build c6d412e

docker-compose(master)>docker-compose --version
docker-compose version 1.11.2, build dfed245

Centos 7 as the host.

Thank you,

Add version on docker hub

Expected behavior:

Add versions for simple down/upgrades

Actual behavior:

Only a main version and no simple way to checkout older version (non-broken version).

Rancher catalog

Any chance to see the Zammad template at https://github.com/rancher/community-catalog ?

FIX: Elasticsearch out of memory after 24 hours.

After 24 hours of install on a 2GB Ram machine, out of memory, changed all "restart:" to unless-stopped as couldn't even stop the thing!.

Add these environment options to docker-compose.yml and then docker-compose up -d again.
ulimits:
memlock: -1
environment:
- bootstrap.memory_lock=true
- "ES_JAVA_OPTS=-Xms100m -Xmx100m"

Worked for me, running smoothly now with:

  zammad-elasticsearch:
    image: zammad/zammad-docker-compose:zammad-elasticsearch
    container_name: elastic
    labels:
      io.rancher.container.pull_image: always
    restart: unless-stopped
    volumes:
      - data-elasticsearch:/usr/share/elasticsearch/data
    ulimits:
      memlock: -1
    environment:
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms100m -Xmx100m"

zammad-railsserver not detecting postgress

Infos:

Docker version: 17.06.1-ce
Docker-compose version: Rancher 1.6.7
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

zammad-railsserver detects postgress and starts.

Actual behavior:

9/28/2017 11:08:03 AMzammad railsserver waiting for postgresql server to be ready...
9/28/2017 11:08:08 AMzammad railsserver waiting for postgresql server to be ready...
9/28/2017 11:08:13 AMzammad railsserver waiting for postgresql server to be ready...
9/28/2017 11:08:18 AMzammad railsserver waiting for postgresql server to be ready...

Steps to reproduce the behavior:

Create a new stack with the following docker-compose.yml

version: '2'
volumes:
  data-zammad:
    driver: local
services:
  zammad-scheduler:
    image: zammad/zammad-docker-compose:zammad-scheduler
    links:
    - postgresql:postgresql
    - zammad:zammad
    - elasticsearch:elasticsearch
    labels:
      io.rancher.container.pull_image: always
  zammad:
    image: zammad/zammad-docker-compose:zammad
    volumes:
    - data-zammad:/home/zammad
    labels:
      io.rancher.container.pull_image: always
      io.rancher.container.start_once: 'true'
  elasticsearch:
    image: zammad/zammad-docker-compose:zammad-elasticsearch
    labels:
      io.rancher.container.pull_image: always
  postgresql:
    image: zammad/zammad-docker-compose:zammad-postgresql
    labels:
      io.rancher.container.pull_image: always
  nginx:
    image: zammad/zammad-docker-compose:zammad-nginx
    volumes:
    - data-zammad:/home/zammad
    links:
    - zammad-websocket:zammad-websocket
    - zammad-railsserver:zammad-railsserver
    ports:
    - 8080:80/tcp
    labels:
      io.rancher.container.pull_image: always
  zammad-railsserver:
    image: zammad/zammad-docker-compose:zammad-railsserver
    links:
    - postgresql:postgresql
    - zammad:zammad
    - elasticsearch:elasticsearch
    labels:
      io.rancher.container.pull_image: always
  zammad-websocket:
    image: zammad/zammad-docker-compose:zammad-websocket
    links:
    - postgresql:postgresql
    - zammad:zammad
    labels:
      io.rancher.container.pull_image: always

New elasticsearch container has no volume

The old elasticsearch image has a volume to persists it's DB:
https://github.com/docker-library/elasticsearch/blob/4369e593bab8b19ea5dc06d70cc2039c3460af46/5/Dockerfile#L60
The new hasn't:
https://github.com/elastic/elasticsearch-docker/blob/master/templates/Dockerfile.j2

This leads to data loss during recreates the containers.

Don't use multiple images

Expected behavior:

Only one image is needed to run a docker-compose environment with containers for single purposes.

As the only difference in the image builds is the entrypoint script you could just merge the entrypoint scripts into one and use command to start the various containers. E.g. https://gist.github.com/hhoechtl/5ec90da9dafb8fdddd403bd7711711c2

This way the services will always have the same and correct version. E.g. if the image build for an image had failed e.g. websockets which would then lead to a mixture of zammad versions in the containers involved in the docker-compose environment.

Actual behavior:

There are various images for the services needed to run a docker-compose environment which means you must synchronize many images with your local registry in order to start an environment with the correct version.

Error running on ubuntu 16.04

hi there,

i get the following message running docker image on ubuntu 16.04

zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready... zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready... zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready... zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready... zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready... zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready... zammad-railsserver_1 | * Listening on tcp://0.0.0.0:3000 zammad-railsserver_1 | Use Ctrl-C to stop zammad-railsserver_1 | 2017-03-16 11:04:42 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.> zammad-railsserver_1 | 2017-03-16 11:04:42 +0000: ENV: {"rack.version"=>[1, 3], "rack.errors"=>#<IO:<STDERR>>, "rack.multithread"=>true, "rack.multiprocess"=>false, "rack.run_once"=>false, "SCRIPT_NAME"=>"", "QUERY_STRING"=>"", "SERVER_PROTOCOL"=>"HTTP/1.1", "SERVER_SOFTWARE"=>"puma 3.6.0 Sleepy Sunday Serenity", "GATEWAY_INTERFACE"=>"CGI/1.2"} zammad-railsserver_1 | --- zammad-railsserver_1 | 2017-03-16 11:04:42 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.> zammad-railsserver_1 | 2017-03-16 11:04:42 +0000: ENV: {"rack.version"=>[1, 3], "rack.errors"=>#<IO:<STDERR>>, "rack.multithread"=>true, "rack.multiprocess"=>false, "rack.run_once"=>false, "SCRIPT_NAME"=>"", "QUERY_STRING"=>"", "SERVER_PROTOCOL"=>"HTTP/1.1", "SERVER_SOFTWARE"=>"puma 3.6.0 Sleepy Sunday Serenity", "GATEWAY_INTERFACE"=>"CGI/1.2"} zammad-railsserver_1 | ---

How can i fix this issue? Any suggestions?

scheduler and websocket reboot in loop after restart

Infos:

Docker version: 17.06
Docker-compose version: 1.15.0
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

All services start normally after host reboot

Actual behavior:

scheduler and websocket reboot in loop

websocket server can access raillsserver now...
bundler: failed to load command: script/websocket-server.rb (script/websocket-server.rb)
Bundler::GemNotFound: Your bundle is locked to clearbit (0.2.7), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of clearbit (0.2.7) has removed it. You'll need to update your bundle to a different version of clearbit (0.2.7) that hasn't been removed in order to install.
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:179:in `rescue in specs'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:173:in `specs'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:233:in `specs_for'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:222:in `requested_specs'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:118:in `block in definition_method'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:19:in `setup'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler.rb:99:in `setup'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/setup.rb:20:in `<top (required)>'
  /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'

scheduler can access raillsserver now...
bundler: failed to load command: script/scheduler.rb (script/scheduler.rb)
Bundler::GemNotFound: Your bundle is locked to clearbit (0.2.7), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of clearbit (0.2.7) has removed it. You'll need to update your bundle to a different version of clearbit (0.2.7) that hasn't been removed in order to install.
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:179:in `rescue in specs'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:173:in `specs'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:233:in `specs_for'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:222:in `requested_specs'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:118:in `block in definition_method'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:19:in `setup'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler.rb:99:in `setup'
  /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/setup.rb:20:in `<top (required)>'
  /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'

Steps to reproduce the behavior:

Restart the host

bundle: command not found

Rancher environment
Docker image zammad/zammad-docker-compose:zammad

1/9/2017 9:13:05 PMcreating db & searchindex...
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 10: bundle: command not found
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 11: bundle: command not found
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 12: bundle: command not found
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 13: bundle: command not found
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 14: bundle: command not found
1/9/2017 9:13:05 PMrm: cannot remove '/home/zammad/log/*.log': No such file or directory
1/9/2017 9:13:05 PMrm: cannot remove '/home/zammad/tmp/pids/*.pid': No such file or directory
1/9/2017 9:13:05 PMstarting zammad...
1/9/2017 9:13:05 PMzammad will be accessable on http://localhost in some seconds
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 24: bundle: command not found
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 25: bundle: command not found
1/9/2017 9:13:05 PM/docker-entrypoint.sh: line 28: bundle: command not found

Railsserver broken

Infos:

Docker version: newest
Docker-compose version: newest
Operating system (Docker host): arch

Expected behavior:

Working railsserver

Actual behavior:

Container is broken

zammad-railsserver_1    | Bundler::GemNotFound: Your bundle is locked to mini_portile2 (2.1.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of mini_portile2 (2.1.0) has removed it. You'll need to update your bundle to a different version of mini_portile2 (2.1.0) that hasn't been removed in order to install.
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:179:in `rescue in specs'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:173:in `specs'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:233:in `specs_for'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:222:in `requested_specs'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:118:in `block in definition_method'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:19:in `setup'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler.rb:99:in `setup'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/setup.rb:20:in `<top (required)>'
zammad-railsserver_1    |   /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
zammad-railsserver_1    |   /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
zammad-railsserver_1    | bundler: failed to load command: rake (/usr/local/bundle/bin/rake)
zammad-railsserver_1    | starting zammad...
zammad-railsserver_1    | zammad will be accessable on http://localhost in some seconds
zammad-railsserver_1    | bundler: failed to load command: puma (/usr/local/bundle/bin/puma)
zammad-railsserver_1    | Bundler::GemNotFound: Your bundle is locked to mini_portile2 (2.1.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of mini_portile2 (2.1.0) has removed it. You'll need to update your bundle to a different version of mini_portile2 (2.1.0) that hasn't been removed in order to install.
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:179:in `rescue in specs'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:173:in `specs'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:233:in `specs_for'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/definition.rb:222:in `requested_specs'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:118:in `block in definition_method'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/runtime.rb:19:in `setup'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler.rb:99:in `setup'
zammad-railsserver_1    |   /usr/local/lib/ruby/gems/2.3.0/gems/bundler-1.13.6/lib/bundler/setup.rb:20:in `<top (required)>'
zammad-railsserver_1    |   /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
zammad-railsserver_1    |   /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'

Endless loop

Steps to reproduce the behavior:

Load newest build

Zammad Backup - Failed to get D-Bus connection

Infos:

Docker version: 17.05.0-ce
Docker-compose version: 1.14.0
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

I want to make a backup with the zammad-backup container and restore ist again.

Actual behavior:

From inside the container I call the zammad_restore.sh script.

root@8356517f7b8b:/home/zammad/contrib/backup# ./zammad_restore.sh
Zammad restored started - Tue Aug 8 10:28:31 UTC 2017!
The restore will delete your current config and database!
Be sure to have a backup available!

Enter 'yes' if you want to proceed!
Restore?: yes
Enter file date to restore:
20170803134310
[...]
20170807132335
File date: 20170807132335
Enter db date to restore:
20170803134310
[...]
20170807132335
DB date: 20170807132335
Stopping Zammad
Failed to get D-Bus connection: Unknown error -1
Restoring Files
Restoring PostgrSQL DB
No passwd entry for user 'postgres'
Starting Zammad
Failed to get D-Bus connection: Unknown error -1
Zammad restored successfully - Tue Aug 8 10:28:42 UTC 2017!

As you could see, I am not able to restore a Backup due to the D-Bus connection Error.

Is this a problem in the restore script itself or did the way to restore changed with the new container?
I could not find any documentation besides the one at https://docs.zammad.org/en/latest/appendix-backup-and-restore.html

kind regards

services.zammad.labels.io.rancher.container.start_once contains true

Hey there,
I'm getting following error..

ERROR: The Compose file './docker-compose.yml' is invalid because:
services.zammad.labels.io.rancher.container.start_once contains true, which is an invalid type, it should be a string, number, or a null

I don't use Rancher, I just cloned the repo and used docker-compose up
Setting services.zammad.labels.io.rancher.container.start_once to "true" or to null fixed this..
Using Arch/Manjaro

docker-compose version 1.9.0, build 25853874
docker-py version: 1.10.6
docker version 1.12.6
Go version: go1.7.4

zammad restore

Infos:

Docker version: 17.06.2-ce
Docker-compose version: 1.11.2
Operating system (Docker host): Ubuntu 16.04.3 LTS

Expected behavior:

restore should work as designed

Actual behavior:

restore not possible

Steps to reproduce the behavior:

get backup of other instance zammad ( v. 2.0.0 )
start zammad (v 2.0.0) docker-compose up -d
copy backupfiles into container docker cp 20170920104238_zammad_files.tar.gz zammaddockercompose_zammad-railsserver_1:/tmp and docker cp 20170920104238_zammad_db.psql.gz zammaddockercompose_zammad-railsserver_1:/tmp
execute container docker exec -ti zammaddockercompose_zammad-railsserver_1 /bin/bash

In Container:

mkdir /var/tmp/zammad_backup
chown -R zammad: /var/tmp/zammad_backup/
cd /home/zammad/contrib/backup/
cp config.dist config
./zammad_restore.sh

root@ca57279d885d:/home/zammad/contrib/backup# ./zammad_restore.sh 

# Zammad restored started - Mon Sep 25 12:25:18 UTC 2017!

The restore will delete your current config and database! 
Be sure to have a backup available! 

Enter 'yes' if you want to proceed!
Restore?: yes
Enter file date to restore: 
20170920104238
File date: 20170920104238
Enter db date to restore: 
20170920104238
DB date: 20170920104238
# Stopping Zammad
Failed to get D-Bus connection: Unknown error -1
# Restoring Files
# Restoring PostgrSQL DB
No passwd entry for user 'postgres'
# Starting Zammad
Failed to get D-Bus connection: Unknown error -1

# Zammad restored successfully - Mon Sep 25 12:25:29 UTC 2017!

root@ca57279d885d:/home/zammad/contrib/backup#

Also I tired to run the setup first and then I try to restore withou success.

Regards,
Sören

Don't build pull requests with travis

Expected behavior:

Travis CI don't run build on every pull requests
Use https://docs.travis-ci.com/user/conditional-builds-stages-jobs/

Actual behavior:

Travis CI tries to build on every pull request and fails because unauthorized
This deceives a problem with the patch

Steps to reproduce the behavior:

Send in a PR

Rancher Catalog Stack deploy failing: Expected state running but got error: Error response from daemon: manifest for zammad/zammad-docker-compose:postgresql not found

Infos:

Docker version: 17.03.1-ce, build c6d412e
Docker-compose version: using Rancher 1.4
Operating system (Docker host): Debian 8

Expected behavior:

Trying to deploy Zammad from Rancher Catalog, using only version avaiable in catalog, 1.2, and expected to deploy smoothly, just like weeks ago.

Actual behavior:

The Postgres, Nginx and ElasticSearch services containers give the same error:

Expected state running but got error: Error response from daemon: manifest for zammad/zammad-docker-compose:postgresql not found
Expected state running but got error: Error response from daemon: manifest for zammad/zammad-docker-compose:nginx not found
Expected state running but got error: Error response from daemon: manifest for zammad/zammad-docker-compose:elasticsearch not found

I've tried to insert my dockerhub user in Rancher registries, but got the same error.

Have anyone experienced this? I've tested the docker-compose in my local machine and worked fine.
Don't understand why it can't pull images. I've tried doing in it in command line:

root@rancher:/home/user# docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username (user): 
Password: 
Login Succeeded
root@rancher:/home/user# docker pull zammad/zammad-docker-compose:elasticsearch
Error response from daemon: manifest for zammad/zammad-docker-compose:elasticsearch not found

any help i'd appreciate.
thks in advance.

SSO via ADFS 2016

Infos:

Docker version: 17.05.0-ce, build 89658be
Docker-compose version: 1.14.0, build c7bdf9e
Operating system (Docker host): Ubuntu Server 16.04

Hi there :)

i know there are some open/closed Issues regarding ADFS and zammad but these are regarding the "old" ADFS 2012r2 und SAML. The new ADFS now supports OAUTH2:

https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/development/enabling-oauth-confidential-clients-with-ad-fs-2016

So i followed the instructions and created an Application Group:

With this Information I filled in the Zammad "Authentication via Generic OAuth2"

Now when I try to logon I get the following "Error-message" with the following Error in "/home/zammad/log/production.log"

I, [2017-07-13T06:04:47.273312 #17] INFO -- : Started GET "/" for 172.18.0.4 at 2017-07-13 06:04:47 +0000
I, [2017-07-13T06:04:47.276834 #17] INFO -- : Processing by InitController#index as HTML
I, [2017-07-13T06:04:47.278520 #17] INFO -- : Rendered init/index.html.erb within layouts/application (0.0ms)
I, [2017-07-13T06:04:47.280073 #17] INFO -- : Completed 200 OK in 3ms (Views: 0.9ms | ActiveRecord: 0.5ms)
I, [2017-07-13T06:04:47.711967 #17] INFO -- : Started POST "/api/v1/signshow" for 172.18.0.4 at 2017-07-13 06:04:47 +0000
I, [2017-07-13T06:04:47.714578 #17] INFO -- : Processing by SessionsController#show as JSON
I, [2017-07-13T06:04:47.714649 #17] INFO -- : Parameters: {"fingerprint"=>"-63209599", "session"=>{"fingerprint"=>"-63209599"}}
I, [2017-07-13T06:04:47.778362 #17] INFO -- : Completed 200 OK in 64ms (Views: 12.4ms | ActiveRecord: 2.4ms)
I, [2017-07-13T06:04:47.790943 #17] INFO -- : Started GET "/api/v1/translations/lang/de-de?=1499925887601" for 172.18.0.4 at 2017-07-13 06:04:47 +0000
I, [2017-07-13T06:04:47.794135 #17] INFO -- : Processing by TranslationsController#lang as JSON
I, [2017-07-13T06:04:47.794192 #17] INFO -- : Parameters: {""=>"1499925887601", "locale"=>"de-de", "translation"=>{}}
I, [2017-07-13T06:04:47.822879 #17] INFO -- : Completed 200 OK in 29ms (Views: 23.5ms | ActiveRecord: 0.5ms)
I, [2017-07-13T06:04:55.329824 #17] INFO -- : Started GET "/auth/oauth2" for 172.18.0.4 at 2017-07-13 06:04:55 +0000
I, [2017-07-13T06:04:55.425828 #17] INFO -- : Started GET "/auth/oauth2/callback?code=[FILTERED]&state=f3ea875cde1d576daadabfb8159b220551bdd645bd395d90" for 172.18.0.4 at 2017-07-13 06:04:55 +0000
F, [2017-07-13T06:04:55.440701 #17] FATAL -- :
Faraday::SSLError (SSL_connect returned=1 errno=0 state=error: certificate verify failed):
/usr/local/lib/ruby/2.3.0/net/http.rb:933:in connect_nonblock' /usr/local/lib/ruby/2.3.0/net/http.rb:933:in connect'
/usr/local/lib/ruby/2.3.0/net/http.rb:863:in do_start' /usr/local/lib/ruby/2.3.0/net/http.rb:852:in start'
/usr/local/lib/ruby/2.3.0/net/http.rb:1398:in request' faraday (0.9.2) lib/faraday/adapter/net_http.rb:82:in perform_request'
faraday (0.9.2) lib/faraday/adapter/net_http.rb:40:in block in call' faraday (0.9.2) lib/faraday/adapter/net_http.rb:87:in with_net_http_connection'
faraday (0.9.2) lib/faraday/adapter/net_http.rb:32:in call' faraday (0.9.2) lib/faraday/request/url_encoded.rb:15:in call'
faraday (0.9.2) lib/faraday/rack_builder.rb:139:in build_response' faraday (0.9.2) lib/faraday/connection.rb:377:in run_request'
oauth2 (1.2.0) lib/oauth2/client.rb:93:in request' oauth2 (1.2.0) lib/oauth2/client.rb:138:in get_token'
oauth2 (1.2.0) lib/oauth2/strategy/auth_code.rb:29:in get_token' omniauth-oauth2 (1.4.0) lib/omniauth/strategies/oauth2.rb:89:in build_access_token'
omniauth-oauth2 (1.4.0) lib/omniauth/strategies/oauth2.rb:73:in callback_phase' omniauth (1.3.1) lib/omniauth/strategy.rb:227:in callback_call'
omniauth (1.3.1) lib/omniauth/strategy.rb:184:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/strategy.rb:186:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/strategy.rb:186:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/strategy.rb:186:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/strategy.rb:186:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/strategy.rb:186:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/strategy.rb:186:in call!' omniauth (1.3.1) lib/omniauth/strategy.rb:164:in call'
omniauth (1.3.1) lib/omniauth/builder.rb:63:in call' rack (1.6.4) lib/rack/etag.rb:24:in call'
rack (1.6.4) lib/rack/conditionalget.rb:25:in call' rack (1.6.4) lib/rack/head.rb:13:in call'
actionpack (4.2.7.1) lib/action_dispatch/middleware/params_parser.rb:27:in call' actionpack (4.2.7.1) lib/action_dispatch/middleware/flash.rb:260:in call'
rack (1.6.4) lib/rack/session/abstract/id.rb:225:in context' rack (1.6.4) lib/rack/session/abstract/id.rb:220:in call'
actionpack (4.2.7.1) lib/action_dispatch/middleware/cookies.rb:560:in call' activerecord (4.2.7.1) lib/active_record/query_cache.rb:36:in call'
activerecord (4.2.7.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in call' actionpack (4.2.7.1) lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
activesupport (4.2.7.1) lib/active_support/callbacks.rb:88:in __run_callbacks__' activesupport (4.2.7.1) lib/active_support/callbacks.rb:778:in _run_call_callbacks'
activesupport (4.2.7.1) lib/active_support/callbacks.rb:81:in run_callbacks' actionpack (4.2.7.1) lib/action_dispatch/middleware/callbacks.rb:27:in call'
actionpack (4.2.7.1) lib/action_dispatch/middleware/remote_ip.rb:78:in call' actionpack (4.2.7.1) lib/action_dispatch/middleware/debug_exceptions.rb:17:in call'
actionpack (4.2.7.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in call' railties (4.2.7.1) lib/rails/rack/logger.rb:38:in call_app'
railties (4.2.7.1) lib/rails/rack/logger.rb:20:in block in call' activesupport (4.2.7.1) lib/active_support/tagged_logging.rb:68:in block in tagged'
activesupport (4.2.7.1) lib/active_support/tagged_logging.rb:26:in tagged' activesupport (4.2.7.1) lib/active_support/tagged_logging.rb:68:in tagged'
railties (4.2.7.1) lib/rails/rack/logger.rb:20:in call' actionpack (4.2.7.1) lib/action_dispatch/middleware/request_id.rb:21:in call'
rack (1.6.4) lib/rack/methodoverride.rb:22:in call' rack (1.6.4) lib/rack/runtime.rb:18:in call'
activesupport (4.2.7.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in call' rack (1.6.4) lib/rack/sendfile.rb:113:in call'
railties (4.2.7.1) lib/rails/engine.rb:518:in call' railties (4.2.7.1) lib/rails/application.rb:165:in call'
railties (4.2.7.1) lib/rails/railtie.rb:194:in public_send' railties (4.2.7.1) lib/rails/railtie.rb:194:in method_missing'
puma (3.6.0) lib/puma/configuration.rb:225:in call' puma (3.6.0) lib/puma/server.rb:578:in handle_request'
puma (3.6.0) lib/puma/server.rb:415:in process_client' puma (3.6.0) lib/puma/server.rb:275:in block in run'
puma (3.6.0) lib/puma/thread_pool.rb:116:in `block in spawn_thread'

/home/zammad/log #

So the problem seems to be "certificate verify failed". The question is which cert?

Thanks for any help :)

Best regards from Nürnberg,
Sebastian

Postgresql volume

I don't see a volumes: section for zammad-postgresql. After running for a few days I did a trial stop and restart and all data was lost. I have all the other images in docker-compose.yml defined with a persistent storage location.
Where is the zammad-postgresql location defined?
I can add a volume line to the .yml, what is the local path for your custom Zammad-posgresql data store?

Zammad container will never start

What is the main task for https://github.com/zammad/zammad-docker-compose/blob/master/docker-compose.yml#L26 container?
It doesn't have the CMD entry https://github.com/zammad/zammad-docker-compose/blob/master/containers/zammad/Dockerfile
So it can't start properly and just continuously rebooting.

New elasticsearch container reboots after update

Infos:

Docker version: 17.06
Docker-compose version: 1.14.0
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

Changed elasticsearch container starts w/o problems

Actual behavior:

The container reboots with org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[/usr/share/elasticsearch/data/docker-cluster]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?

Steps to reproduce the behavior:

Update from previous docker-compose with elasticsearch image to docker.elastic.co/elasticsearch/elasticsearch:5.5.0

I think it's an permission issue inside the volume. Will check that.

Change versions

Hello

Is there a way to change the installation to use the development branch / 2.0 version ?

Thanks

"Loading..." on latest build.

I am no longer able to start a clean installation of Zammad (using docker compose) after the very latest built images on docker hub. It may work the first time everything is booted up, but fails on subsequent restarts with the web interface returning error 404's for CSS and JS files used to render the web frontend.

Infos:

Docker version: 17.05.0-ce
Docker-compose version: 1.11.2
Operating system (Docker host): Ubuntu 16.04 LTS

Expected behavior:

The application web interface is accessible.

Actual behavior:

A blank screen with the text "Loading..." appears. The browser console has JS and CSS errors indicating that the bundled / build CSS and JS files are missing (404).

Steps to reproduce the behavior:

Start the application via docker-compose. Restart the containers.

Commands are executed in / instead of /home/zammad

Infos:

Docker version: 17.06
Docker-compose version: 0.12.1
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

Commands should be executed in the application folder /home/zammad

Actual behavior:

Commands are executed in /

Steps to reproduce the behavior:

docker-compose exec zammad-railsserver rails c

The WORKDIR should be set to /home/zammad

Elasticsearch image is deprecated

See: https://hub.docker.com/_/elasticsearch/

Zammad in docker (how to update)

Is there a dedicated instructions on how to update zammad in docker container?

Will pulling container files from github and down/up be sufficient?

Be able to use reverse / SSL proxy

Infos:

Docker version: 17.09
Docker-compose version: 1.16.1
Operating system (Docker host): Ubuntu 16.04

Expected behavior:

Run zammad with a reverse proxy like jwilder/nginx-proxy

Actual behavior:

The docker-compose.yml maps container port 80 to host port 80
It's not possible to map a port twice

Steps to reproduce the behavior:

Start a reverse proxy that maps port 80 and 443 and then start zammad

Possible solution

Use https://docs.docker.com/compose/extends/#multiple-compose-files
Move the mapping of port 80 to docker-compose.override.yml
Add a docker-compose.prod.yml as example how to connect to the external reverse proxy
This would be non breaking because the docker-compose.override.yml is always used if it exists.

If you're ok with this I could prepare a PR.

zammad-postgresql fails to start

Infos:

Docker version: 17.09.0-ce
Docker-compose version: 1.17.0
Operating system (Docker host): Ubuntu 16.04.3
I reproduced the behavior using Docker for Windows at my local machine.

Expected behavior:

Service zammad-postgresql should startup.

Actual behavior:

Startup of service zammad-postgresql fails with:

FATAL:  database "zammad_production" does not exist
LOG:  incomplete startup packet

Steps to reproduce the behavior:

Clone git repo
Run docker-compose.yml with docker-compose up -d

Best practice for nginx-proxy configuration and host-based volumes

Hi there!
So there are these docker-containers that help you out setting up multiple internet-accessible docker-containers on the same server:

https://github.com/jwilder/nginx-proxy
- or combination of nginx and https://github.com/jwilder/docker-gen
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion

I'm using the combination of nginx, docker-gen and the companion to provide my docker containers to the internet.

At first it seemed to work with zammad (I just had to set the client_max_body_size specifically in the vhost.d), but actually I seem to have a problem with the websocket part.
I can't get the livechat to work; whenever I try to access */ws it says bad gateway.

I've set up the whole thing by exposing port 80 on the zammad-nginx container and using it as VIRTUAL_PORT for the docker-gen.

Any ideas what I'm missing here?

Scheduler not working

Infos:

Docker version: 17.05.0-ce
Docker-compose version: 1.9.0, build 2585387
Operating system (Docker host): Ubuntu 16.04.3 LTS

Expected behavior:

Scheduler running and monitoring showing state run

Actual behavior:

Scheduler container is running and shows message scheduler can access raillsserver now...
Railsserver is running but no mails are received
Opening the Monitoring tab shows scheduler not running

Steps to reproduce the behavior:

I just updated my old environment which was running Zammad 1.5.0 to 2.1.1 with my images built from this repository but tagged with 2.1.1 as there's currently no image with that version tag.

Deploy current docker-compose version

The railsserver seems to be running as expected, the log doesn't show any useful hints:

14.10.2017 18:26:11drop indexes...
14.10.2017 18:26:11create indexes...
14.10.2017 18:26:11reload data...
14.10.2017 18:26:11 reload Organization
14.10.2017 18:26:11  - started at 2017-10-14 16:26:11 UTC
14.10.2017 18:26:12  - took 0 seconds
14.10.2017 18:26:12 reload User
14.10.2017 18:26:12  - started at 2017-10-14 16:26:12 UTC
14.10.2017 18:26:22  - took 10 seconds
14.10.2017 18:26:22 reload Ticket
14.10.2017 18:26:22  - started at 2017-10-14 16:26:22 UTC
14.10.2017 18:32:01  - took 338 seconds
14.10.2017 18:32:01starting zammad...
14.10.2017 18:32:01zammad will be accessable on http://localhost in some seconds
14.10.2017 18:32:01Puma starting in single mode...
14.10.2017 18:32:01* Version 3.9.1 (ruby 2.4.1-p111), codename: Private Caller
14.10.2017 18:32:01* Min threads: 5, max threads: 30
14.10.2017 18:32:01* Environment: production
14.10.2017 18:32:04* Listening on tcp://0.0.0.0:3000
14.10.2017 18:32:04Use Ctrl-C to stop
14.10.2017 18:32:102017-10-14T16:32:10Z:client(6981477649) request spool data > '2017-10-14T16:21:27Z'
14.10.2017 18:32:102017-10-14T16:32:10Z:client(6981477649) send spool:sent event
14.10.2017 18:32:112017-10-14T16:32:11Z:client(6981477649) do not send broadcast to it self
14.10.2017 18:32:262017-10-14 16:32:26 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:26---
14.10.2017 18:32:302017-10-14 16:32:30 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:30---
14.10.2017 18:32:342017-10-14 16:32:34 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:34---
14.10.2017 18:32:382017-10-14 16:32:38 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:38---
14.10.2017 18:32:422017-10-14 16:32:42 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:42---
14.10.2017 18:32:472017-10-14 16:32:47 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:47---
14.10.2017 18:32:512017-10-14 16:32:51 +0000: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
14.10.2017 18:32:51---

Zammad container exits with 'Switch to inspect mode'

Hi there, I'm trying to use these compose file and images but can't get the zammad container to start without starting it manually with docker run -it zammad/zammad-docker-compose:zammad. It only works with the -it flags.

Am I missing something here?

Infos:

Docker version: 17.05.0-ce, build 89658e
Docker-compose version: 1.7.0
Operating system (Docker host): Debian 8.9

I have tested this with 44 and 45.

Expected behavior:

Zammad container should start and keep running

Actual behavior:

Zammad container prints only "Switch to inspect mode" and exits

Steps to reproduce the behavior:

git clone, docker-compose up, waiting, zammad container does not recover.

websocket server waiting for zammads railsserver to be ready

Greetings,

I'm running Dock Container Zammad on my local host. Unfortunately cant reach Zammad webportal on my local host. I just removed all my previous zammad dock containers with "rm -R" and cleaned up unused images and containers of docker. Then cloned latest version of Zammad into new directory.

When execute "Docker-compose up":
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-postgresql_1 | LOG: incomplete startup packet
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-railsserver_1 | creating db & searchindex...
zammad-railsserver_1 | bundler: failed to load command: rake (/usr/local/bundle/bin/rake)
zammad-railsserver_1 | Bundler::GemNotFound: Your bundle is locked to i18n (0.7.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of i18n (0.7.0) has removed it. You'll need to update your bundle to a different version of i18n (0.7.0) that hasn't been removed in order to install.
.
.
.
zammad-railsserver_1 | /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require' zammad-railsserver_1 | /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:inrequire'
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-scheduler_1 | scheduler waiting for zammads railsserver to be ready...
zammad-websocket_1 | websocket server waiting for zammads railsserver to be ready...
running "docker-compose ps":
zammad-docker-compose(master)> docker-compose ps
Name Command State Ports

zammaddockercompose_za /docker-entrypoint.sh Up 9200/tcp, 9300/tcp
mmad-elasticsearch_1 elas ...
zammaddockercompose_za nginx -g daemon off; Up 443/tcp, 80/tcp,
mmad-nginx_1 0.0.0.0:8881->88/tcp
zammaddockercompose_za docker-entrypoint.sh Up 5432/tcp
mmad-postgresql_1 postgres
zammaddockercompose_za /docker-entrypoint.sh Restarting
mmad-railsserver_1 zamm ...
zammaddockercompose_za /docker-entrypoint.sh Up
mmad-scheduler_1 zamm ...
zammaddockercompose_za /docker-entrypoint.sh Up 6042/tcp
mmad-websocket_1 zamm ...
zammaddockercompose_za irb Exit 0

My docker ps status is as:
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
db7d99e129d8 zammad/zammad-docker-compose:zammad-nginx "nginx -g 'daemon ..." 13 minutes ago Up 13 minutes 80/tcp, 443/tcp, 0.0.0.0:8881->88/tcp zammaddockercompose_zammad-nginx_1
33f31c5a49ff zammad/zammad-docker-compose:zammad-scheduler "/docker-entrypoin..." 31 minutes ago Up 14 minutes zammaddockercompose_zammad-scheduler_1
a8ba9c34a1e6 zammad/zammad-docker-compose:zammad-websocket "/docker-entrypoin..." 31 minutes ago Up 14 minutes 6042/tcp zammaddockercompose_zammad-websocket_1
4a6c81e4418f zammad/zammad-docker-compose:zammad-railsserver "/docker-entrypoin..." 31 minutes ago Restarting (1) 6 minutes ago zammaddockercompose_zammad-railsserver_1
b31aa471fea1 zammad/zammad-docker-compose:zammad-elasticsearch "/docker-entrypoin..." About an hour ago Up 14 minutes 9200/tcp, 9300/tcp zammaddockercompose_zammad-elasticsearch_1
ca64ade67f43 zammad/zammad-docker-compose:zammad-postgresql "docker-entrypoint..." About an hour ago Up 14 minutes 5432/tcp zammaddockercompose_zammad-postgresql_1

my inner docker-config of zammad as:
zammad-docker-compose(master)> cat docker-compose.yml
version: '3'

services:

zammad:
depends_on:

zammad-elasticsearch
zammad-postgresql
image: zammad/zammad-docker-compose:zammad
labels:
io.rancher.container.pull_image: always
io.rancher.container.start_once: 'true'
restart: on-failure
volumes:
data-zammad:/home/zammad

zammad-elasticsearch:
image: zammad/zammad-docker-compose:zammad-elasticsearch
labels:
io.rancher.container.pull_image: always
restart: always

zammad-nginx:
depends_on:

zammad
image: zammad/zammad-docker-compose:zammad-nginx
labels:
io.rancher.container.pull_image: always
links:
zammad-railsserver
zammad-websocket
ports:
"8881:88" //since I was facing with error of already listening to port 0.0.0.0:80 I changed it like this
restart: always
volumes:
data-zammad:/home/zammad

zammad-postgresql:
image: zammad/zammad-docker-compose:zammad-postgresql
labels:
io.rancher.container.pull_image: always
restart: always

zammad-railsserver:
depends_on:

zammad
image: zammad/zammad-docker-compose:zammad-railsserver
labels:
io.rancher.container.pull_image: always
links:
zammad-elasticsearch
zammad-postgresql
depends_on:
zammad
restart: always
volumes:
data-zammad:/home/zammad

zammad-scheduler:
depends_on:

zammad
image: zammad/zammad-docker-compose:zammad-scheduler
labels:
io.rancher.container.pull_image: always
links:
zammad-elasticsearch
zammad-postgresql
restart: always
volumes:
data-zammad:/home/zammad

zammad-websocket:
depends_on:

zammad
image: zammad/zammad-docker-compose:zammad-websocket
labels:
io.rancher.container.pull_image: always
links:
zammad-postgresql
zammad
restart: always
volumes:
data-zammad:/home/zammad
volumes:
data-zammad:
driver: local

Im using Centos 7, Docker version 17.03.1-ce, and ruby 2.0.0.
Thank you in advance,

Avoid duplicate configuration in docker-compose.yml and docker-compose-build.yml

docker-compose is able to override/concatenate multiple configurations.
https://docs.docker.com/compose/extends/#example-use-case
ATM. moste of the configuration of docker-compose.yml and docker-compose-build.yml are the same.
This could be avoided by build with
docker-compose -f docker-compose.yml -f docker-compose-build.yml

Configuration that must not be set for build could be moved to docker-compose.override.yml as it is loaded by default if no docker-compose file is specified to load.

Google Auth 500 error

I, [2017-01-12T06:30:08.658823 #24]  INFO -- : Started GET "/auth/google_oauth2" for *** at 2017-01-12 06:30:08 +0000
I, [2017-01-12T06:30:09.094937 #24]  INFO -- : Started GET "/auth/google_oauth2/callback?state=c57f7baa9f3e3f08c6838ef0e2e72600d4f9be1cf294f851&code=[FILTERED]" for *** at 2017-01-12 06:30:09 +0000
F, [2017-01-12T06:30:09.136321 #24] FATAL -- : 
Faraday::SSLError (SSL_connect returned=1 errno=0 state=error: certificate verify failed):
  /usr/local/lib/ruby/2.3.0/net/http.rb:933:in `connect_nonblock'
  /usr/local/lib/ruby/2.3.0/net/http.rb:933:in `connect'
  /usr/local/lib/ruby/2.3.0/net/http.rb:863:in `do_start'
  /usr/local/lib/ruby/2.3.0/net/http.rb:852:in `start'
  /usr/local/lib/ruby/2.3.0/net/http.rb:1398:in `request'
  faraday (0.9.2) lib/faraday/adapter/net_http.rb:82:in `perform_request'
  faraday (0.9.2) lib/faraday/adapter/net_http.rb:40:in `block in call'
  faraday (0.9.2) lib/faraday/adapter/net_http.rb:87:in `with_net_http_connection'
  faraday (0.9.2) lib/faraday/adapter/net_http.rb:32:in `call'
  faraday (0.9.2) lib/faraday/request/url_encoded.rb:15:in `call'
  faraday (0.9.2) lib/faraday/rack_builder.rb:139:in `build_response'
  faraday (0.9.2) lib/faraday/connection.rb:377:in `run_request'
  oauth2 (1.2.0) lib/oauth2/client.rb:93:in `request'
  oauth2 (1.2.0) lib/oauth2/client.rb:138:in `get_token'
  oauth2 (1.2.0) lib/oauth2/strategy/auth_code.rb:29:in `get_token'
  omniauth-google-oauth2 (0.4.1) lib/omniauth/strategies/google_oauth2.rb:107:in `custom_build_access_token'
  omniauth-oauth2 (1.4.0) lib/omniauth/strategies/oauth2.rb:73:in `callback_phase'
  omniauth (1.3.1) lib/omniauth/strategy.rb:227:in `callback_call'
  omniauth (1.3.1) lib/omniauth/strategy.rb:184:in `call!'
  omniauth (1.3.1) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.3.1) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.3.1) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.3.1) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.3.1) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.3.1) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.3.1) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.3.1) lib/omniauth/builder.rb:63:in `call'
  rack (1.6.4) lib/rack/etag.rb:24:in `call'
  rack (1.6.4) lib/rack/conditionalget.rb:25:in `call'
  rack (1.6.4) lib/rack/head.rb:13:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/flash.rb:260:in `call'
  rack (1.6.4) lib/rack/session/abstract/id.rb:225:in `context'
  rack (1.6.4) lib/rack/session/abstract/id.rb:220:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/cookies.rb:560:in `call'
  activerecord (4.2.7.1) lib/active_record/query_cache.rb:36:in `call'
  activerecord (4.2.7.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.2.7.1) lib/active_support/callbacks.rb:88:in `__run_callbacks__'
  activesupport (4.2.7.1) lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
  activesupport (4.2.7.1) lib/active_support/callbacks.rb:81:in `run_callbacks'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.2.7.1) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.2.7.1) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.2.7.1) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.2.7.1) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.2.7.1) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.2.7.1) lib/rails/rack/logger.rb:20:in `call'
  actionpack (4.2.7.1) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
  rack (1.6.4) lib/rack/runtime.rb:18:in `call'
  activesupport (4.2.7.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
  rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
  railties (4.2.7.1) lib/rails/engine.rb:518:in `call'
  railties (4.2.7.1) lib/rails/application.rb:165:in `call'
  railties (4.2.7.1) lib/rails/railtie.rb:194:in `public_send'
  railties (4.2.7.1) lib/rails/railtie.rb:194:in `method_missing'
  puma (3.6.0) lib/puma/configuration.rb:225:in `call'
  puma (3.6.0) lib/puma/server.rb:578:in `handle_request'
  puma (3.6.0) lib/puma/server.rb:415:in `process_client'
  puma (3.6.0) lib/puma/server.rb:275:in `block in run'
  puma (3.6.0) lib/puma/thread_pool.rb:116:in `block in spawn_thread'

Chat: Problem on custum port

Hello,

When taking a custum port on docker there are problems with the chat:
http://support.local:2218/assets/chat/chat.min.js => 404 Not Found