Argo Emissary Executor Quick Fix - Emissary-Specific Issues

Argo Workflows emissary executor uses a sidecar proxy for container management. Emissary-specific configuration errors cause pod startup failures or missing artifacts. This guide covers the fix.

Quick Fix

Wrong

config: |
  containerRuntimeExecutor: emissary
  executor:
    volumeMounts:
    - name: docker-socket
      mountPath: /var/run/docker.sock

The issue: emissary does not use Docker socket. Mounting it is unnecessary and causes permission errors. Emissary uses the Kubernetes API instead.

Right

config: |
  containerRuntimeExecutor: emissary
  executor:
    imagePullPolicy: IfNotPresent
    resources:
      requests:
        cpu: 100m
        memory: 64Mi
      limits:
        cpu: 500m
        memory: 256Mi

# Expected output after applying the fix
# Emissary sidecar starts correctly
# No Docker socket dependency
# Resource limits prevent sidecar from starving steps
# Workflow pod initializes and runs steps

Prevention

• Do not mount Docker socket with emissary executor
• Set resource requests/limits for the emissary sidecar
• Use imagePullPolicy: IfNotPresent to reduce network requests
• Verify emissary compatibility with your container runtime
• Test with containerRuntimeExecutor: emissary before production rollout

DodaTech Tools

Doda Browser's emissary diagnostics check sidecar health and resource usage. DodaZIP archives executor configurations for standardization. Durga Antivirus Pro validates executor security settings.

FAQ