Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Put Dockerfile for zammad/zammad docker hub image in repo #215

Closed
senk opened this issue Oct 19, 2016 · 7 comments
Closed

Put Dockerfile for zammad/zammad docker hub image in repo #215

senk opened this issue Oct 19, 2016 · 7 comments
Assignees

Comments

@senk
Copy link
Contributor

senk commented Oct 19, 2016

Please put the Dockerfile in the repo so it is clear how the docker hub image is build.
Plus it can be improved by the community

@thorsteneckel
Copy link
Contributor

thorsteneckel commented Oct 19, 2016

Hi @senk - we will provide the Docker repository shortly. I'll update this issue accordingly.

@celevra
Copy link

celevra commented Oct 19, 2016

the docker image is not usable, so it would be nice to see the dockerfile:

core@core1 ~ $ docker run --name=ticketsystem --env HOSTNAME=xxx --env PORT=80 --env REGISTER=true --env EXTERNALIP=xxx zammad/zammad
Starting postgresql-9.6 service: [  OK  ]
error: "Read-only file system" setting key "vm.max_map_count"
Starting elasticsearch: [  OK  ]
Starting postfix: [  OK  ]
Starting nginx: nginx: [warn] duplicate MIME type "text/html" in /etc/nginx/conf.d/zammad.conf:27
[  OK  ]
core@core1 ~ $

@celevra
Copy link

celevra commented Oct 19, 2016

it is a timing issue, zammed is starting before the database is ready and panics

@senk
Copy link
Contributor Author

senk commented Oct 19, 2016

That issue is discussed in #213

Am 19.10.2016 um 19:16 schrieb celevra <notifications@github.commailto:notifications@github.com>:

it is a timing issue, zammed is starting before the database is ready and panics

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//issues/215#issuecomment-254879768, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AArXqGkI1srUDpukOIez_58-mZnRhznkks5q1lBXgaJpZM4KbKAx.

@SISheogorath
Copy link

The whole Dockerfile is more or less broken. As it starts all services inside a single container. You should provide a docker-compose.yml to orchestrate the containers. Having one container per service would be the right way.

Refering to: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/run-only-one-process-per-container

@celevra
Copy link

celevra commented Oct 20, 2016

here is a working Dockerfile with a single container
https://github.com/celevra/zammad-docker

@thorsteneckel
Copy link
Contributor

Hi @ALL we synced to docker repository to github. You can check it out and im improve it: https://github.com/zammad/docker

As @SISheogorath mentioned correctly we start all services inside a single container (against the docker best practices). We decided to go this way to make testing zammad as easy as possible. We're planning to create a docker-compose.yml version as soon as possible but have a lot to do right no. So maybe some open source docker hero will step up and help us out here. Would be much appreciated 😍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants