database.yml is in the wrong location for docker containers

[JasperE84]

Used Zammad Version

6.3.1

Environment

• Installation method: docker-compose

Actual behaviour

Scheduler container's log shows errors causing scheduled jobs to fail if using default docker-compose setup:
ConnectionTimeoutError: could not obtain a connection from the pool within 5.000 seconds (waited 5.000 seconds); all pooled connections were in use.

Runtime pool size of 5 isn't equal to value of 50 configured in default rails database.yml:

$ docker compose run --rm zammad-scheduler rails r "p ActiveRecord::Base.connection_pool.stat"
[+] Creating 3/0
 ✔ Container docker_zammad-zammad-memcached-1   Running                                                                                            0.0s
 ✔ Container docker_zammad-zammad-redis-1       Running                                                                                            0.0s
 ✔ Container docker_zammad-zammad-postgresql-1  Running                                                                                            0.0s
I, [2024-05-17T08:31:11.773981 #1]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2024-05-17T08:31:11.824991#1-6060]  INFO -- : Using memcached as Rails cache store.
I, [2024-05-17T08:31:11.825266#1-6060]  INFO -- : Using the Redis back end for Zammad's web socket session store.
{:size=>5, :connections=>0, :busy=>0, :dead=>0, :idle=>0, :waiting=>0, :checkout_timeout=>5.0}

When copying the default rails database.yml and mounting it in docker as such, problem is solved:

x-shared:
  zammad-service: &zammad-service
    environment: &zammad-environment
      [..snip..]
    volumes:
      - ./tempdb.yml:/opt/zammad/config/database.yml

I think the fix should be something like contrib/docker/docker-entrypoint.sh checking for existing ~/config/database.yml symlink to ~/config/database/database.yml and creating it if it doesnt exist. Or move database.yml from its subdirectory to /config/ directly.

More info here:
https://community.zammad.org/t/scheduler-fails-with-activerecord-could-not-obtain-a-connection-from-the-pool-within-5-000-seconds-waited-5-000-seconds-all-pooled-connections-were-in-use/14320/7

Expected behaviour

Scheduled jobs finish without problems

Steps to reproduce the behaviour

$ docker-compose up -d

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes

[JasperE84]

So basically this function seems to be missing in docker entry point:

zammad/contrib/packager.io/functions

Line 172 in 0a0935d

function update_database_yml () {

[Keridos]

Can confirm that this happened on our 6.3.1 deployment, too. Adding a bind mount with a correct database.yml file to /opt/zammad/config/database.yml fixes the symptoms.

[mgruner]

Please update your .env instead to the latest state from upstream. There is a new variable POSTGRESQL_OPTIONS=?pool=50 which is required now.

https://github.com/zammad/zammad-docker-compose/blob/master/.env