Argo Workflows Daemon Quick Fix - Daemon Container Errors

Argo Workflows daemon containers run long-lived services alongside workflow steps. Misconfigured daemons fail to start or block workflow completion. This guide covers the fix.

Quick Fix

Wrong

templates:
- name: with-daemon
  daemon:
    name: db-proxy
    image: postgres:15

The issue: missing lifecycle hooks, no readinessProbe, and no environment variables for the daemon. The database may not be ready when steps try to connect, and the daemon may not shut down properly.

Right

templates:
- name: with-daemon
  daemon:
    name: db-proxy
    image: postgres:15-alpine
    env:
    - name: POSTGRES_PASSWORD
      value: temp-pw
    readinessProbe:
      exec:
        command: ["pg_isready"]
      initialDelaySeconds: 5
    lifecycle:
      preStop:
        exec:
          command: ["pg_ctl", "stop"]

# Expected output after applying the fix
# Daemon "db-proxy" starts and passes readiness probe
# Steps connect to postgres on localhost:5432
# Daemon terminates after all steps complete
# Workflow completes successfully

Prevention

• Always add readinessProbe to daemon containers
• Set environment variables required by the daemon image
• Use lifecycle.preStop for graceful shutdown
• Expose daemon ports for step containers to connect
• Use lightweight images for daemon containers to reduce startup time

DodaTech Tools

Doda Browser's daemon manager shows daemon status, logs, and health checks. DodaZIP archives daemon configurations. Durga Antivirus Pro scans daemon images for vulnerabilities.

FAQ