zammad / zammad-docker-compose Goto Github PK
View Code? Open in Web Editor NEWZammad 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 images for docker-compose
Home Page: https://hub.docker.com/r/zammad/zammad-docker-compose/
License: GNU Affero General Public License v3.0
Hello,
I try to install this in a container, how can i change the port (for outside)?
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?
docker-compose up -d
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
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
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.
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
If you're ok with this I could prepare a PR.
The WORKDIR should be set to /home/zammad
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.
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?
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
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,
Any chance to see the Zammad template at https://github.com/rancher/community-catalog ?
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"
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?
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?
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:
image: zammad/zammad-docker-compose:zammad-elasticsearch
labels:
io.rancher.container.pull_image: always
restart: always
zammad-nginx:
depends_on:
zammad-postgresql:
image: zammad/zammad-docker-compose:zammad-postgresql
labels:
io.rancher.container.pull_image: always
restart: always
zammad-railsserver:
depends_on:
zammad-scheduler:
depends_on:
zammad-websocket:
depends_on:
Im using Centos 7, Docker version 17.03.1-ce, and ruby 2.0.0.
Thank you in advance,
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.
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.
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
Hi there!
So there are these docker-containers that help you out setting up multiple internet-accessible docker-containers on the same server:
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?
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.
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:
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
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'
scheduler can access raillsserver now...
scheduler not running
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.
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---
I want to run a Zammad docker-compose environment with a defined stable version of zammad e.g. "2.1.1".
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.
Starting the Rails container.
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'
docker-compose pull && docker-compose up
Looks like this issue is related to 89473cc
I get 503 error, nginx-proxy doesn't understand what to do with it.
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.
Hello
Is there a way to change the installation to use the development branch / 2.0 version ?
Thanks
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.
Is there a dedicated instructions on how to update zammad in docker container?
Will pulling container files from github and down/up be sufficient?
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
FATAL: database "zammad_production" does not exist
LOG: incomplete startup packet
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?
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'
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?
zammad-railsserver detects postgress and starts.
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...
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
I think it's an permission issue inside the volume. Will check that.
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.
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.
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.
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
/var/tmp/zammad_backup/
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.
zammad-railsserver
using docker exec -it zammad-railsserver bash
/home/zammad/contrib/backup/zammad_backup.sh
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.
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
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?
I have tested this with 44 and 45.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.