Files
computer-playbook/roles/docker-container
Kevin Veen-Birkenbach e09f561f0b Refactor run-once orchestration and bootstrap Mailu/Mastodon in a single deploy
- Replace legacy utils/run_once.yml with the new helpers utils/once_flag.yml and utils/once_finalize.yml
- Introduce utils/compose_up.yml to ensure docker-compose stacks are up and to flush handlers safely without coupling to run-once flags
- Migrate all affected roles (desk-*, dev-*, sys-ctl-*, sys-svc-*, web-app-*, web-svc-*, util-*) to the new run-once helpers
- Rework sys-svc-msmtp to auto-load Mailu once per deploy, check reachability, and reuse the running stack instead of requiring multiple playbook passes
- Adjust web-app-mailu to integrate cert deployment, handler flushing, and run-once handling so Mailu is fully initialized in a single deploy
- Improve Matomo, CDN, logout and CSP/health-check related roles to cooperate with the new compose_up / once_* pattern
- Simplify alarm/backup/timer/service orchestration (sys-ctl-alm-*, sys-bkp-provider, sys-timer-cln-bkps, etc.) by moving run-once logic into dedicated 01_core.yml files
- Update integration tests so utils/once_flag.yml and utils/once_finalize.yml are recognised as valid run-once providers, keeping the global run_once_* guarantees consistent
- Align frontend injection and service dependencies so Mastodon- and Mailu-related services can be brought up coherently within a single deployment cycle rather than several iterations
2025-12-01 13:30:50 +01:00
..

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> when central_database feature is enabled
    • central_ldap when LDAP feature and network are enabled
    • default
  • depends_on_dmbs.yml.j2
    Builds a depends_on: block automatically:

    • If central_database is off, renders an empty list depends_on: []
    • Otherwise, includes database and/or redis with healthcheck conditions
  • healthcheck/
    Four strategies:

    • curl.yml.j2 (HTTP via curl -f)
    • wget.yml.j2 (HTTP via wget --spider)
    • tcp.yml.j2 (TCP socket test)
    • msmtp_curl.yml.j2 (SMTP first, then HTTP via curl; 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.

  • Featuredriven logic
    Networks and dependencies adjust automatically based on your applications variables.

  • Multiple healthcheck options
    Pick the probe that works best for your containers protocol and requirements.

Further Resources