Ensure that the database host alias is only attached to the database containers themselves, not to dependent application containers. This avoids DNS collisions where multiple containers expose the same alias (e.g. 'postgres') on the same network, which led to connection refused errors in XWiki. See conversation: https://chatgpt.com/share/68cae4e5-94e4-800f-b291-d2acdb36af21
Docker Container
Description
This Ansible role supplies common Jinja2 snippets for composing Docker services consistently. Rather than repeating the same YAML blocks, you include one or more of the provided templates in your docker-compose.yml.j2.
Overview
The following templates are available under roles/docker-container/templates/:
-
base.yml.j2
Common service settings:restart,env_file,logging. -
networks.yml.j2
Conditional network attachments:central_<database_type>whencentral_databasefeature is enabledcentral_ldapwhen LDAP feature and network are enableddefault
-
depends_on_dmbs.yml.j2
Builds adepends_on:block automatically:- If
central_databaseis off, renders an empty listdepends_on: [] - Otherwise, includes
databaseand/orrediswith healthcheck conditions
- If
-
healthcheck/
Four strategies:curl.yml.j2(HTTP viacurl -f)wget.yml.j2(HTTP viawget --spider)tcp.yml.j2(TCP socket test)msmtp_curl.yml.j2(SMTP first, then HTTP viacurl; avoids duplicate emails)
Include whichever snippets your service requires to keep your Compose files DRY and maintainable.
Features
-
Modular templates
Mix only the blocks you need. -
Feature‐driven logic
Networks and dependencies adjust automatically based on yourapplicationsvariables. -
Multiple healthcheck options
Pick the probe that works best for your container’s protocol and requirements.