The reason zammad-init container can't not connect Postgres some time

[chendelin1982]

Infos

• Docker version: latest
• Docker-compose version: lastest
• Operating system (Docker host):

Expected behavior

I found the reason that some time zammad-init container can't not connect Postgres.

Because that zammad-init container will use PostgreSQL URI for connection to Postgres, and you know that PostgreSQL URI have some special string limit

• DB hostname: zammad_01uh9-postgresql can not used, but zammad-postgresql is OK
• DB password: 1PrMxExC45LsCT%#@&! can not used, but 1PrMxExC45LsCT is OK

Actual behavior

*

Steps to reproduce the behavior

*

[mgruner]

Hi @chendelin1982. I'm not sure this is actually a bug in Zammad. Using zammad-01uh9-postgresql instead of zammad_01uh9-postgresql does work, so it is probably not a length limit of the string.

Please feel free to provide more information if you believe this is a bug in the Zammad codebase.

[chendelin1982]

Hi @chendelin1982. I'm not sure this is actually a bug in Zammad. Using zammad-01uh9-postgresql instead of zammad_01uh9-postgresql does work, so it is probably not a length limit of the string.

Please feel free to provide more information if you believe this is a bug in the Zammad codebase.

Hi, thanks for your reply. I need to clarify my previous description. It shouldn't be a length limit, but rather a format limit. The Zammad container used a URI for the database connection.

In URI standards, the hostname part (also known as the network location or authority) typically follows DNS specifications, which means it should be a valid domain name or IP address. According to DNS specifications, hostnames can include letters, numbers, and hyphens (-), but cannot contain underscores (_).

If you have used an underscore in the URI, this could be the reason for the URI::InvalidURIError.