-
Notifications
You must be signed in to change notification settings - Fork 229
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
What's wrong with Zammad 6 on docker compose ? #365
Comments
The current docker-compose.yml is broken. Postgresql client config is missing. Also upgrade to version 6 requires manual migration of the data. see #348 (comment) |
There are many problems with zammad 6. I'm surprised this version has been released. |
Please don't confuse compose / docker Zammad with Zammad itself. Zammad 6 itself is running great. |
OK thx |
Should be fixed by #366 |
Solved by 7f31a9a. |
I am trying to run Zammad 6 on docker compose and still having problems. As if variables are not passed between containers, for example Postgres variables. I tested on Debin 12 and Ubuntu Server 22.04.
If I run Zammad 5.4 on the same systems there is no problem.
Infos
root@test2:~/docker/zammad-docker-compose# cat .env ELASTICSEARCH_VERSION=8.8.0 IMAGE_REPO=ghcr.io/zammad/zammad MEMCACHE_SERVERS=zammad-memcached:11211 MEMCACHE_VERSION=1.6.20-alpine POSTGRES_DB=zammad_production POSTGRES_PASS=zammad POSTGRES_USER=zammad POSTGRES_HOST=zammad-postgresql POSTGRES_PORT=5432 POSTGRES_VERSION=15.3-alpine REDIS_URL=redis://zammad-redis:6379 REDIS_VERSION=7.0.5-alpine RESTART=always VERSION=6.0.0-66
Steps to reproduce the behavior
Logs:
Checking variables:
Why ?
The text was updated successfully, but these errors were encountered: