Argo-workflow-exec

Bitnami secure container image for Argo Workflows, an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes.

  • Automation
  • Development
  • Tools & Utilities
Bitnami secure container image for Argo Workflows, an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
100last commit 3 days ago
Popular
8517,104 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
17,104
Open issues
1396
Last commit
2026-11-18
Latest release
v4.1.6
License
Apache-2.0
Activity
steady

Checked 3 days ago - source: GitHub (argoproj/argo-workflows)

Resources & Compatibility

Requirements not published yet.

Checked 23 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Preview ApplicationSets before creating Before creating an ApplicationSet (a template that tells Argo CD which apps to make), add `--dry-run` to `argocd appset create <file>` so it only previews the apps it would manage. This catches typos or unwanted apps before a real creation goes live. source
  • Start the dashboard safely If you need the Argo CD web UI, run `argocd admin dashboard` with `--address 127.0.0.1` and a free `--port`, for example 8080. That keeps the dashboard on your local machine and avoids a busy port stopping it from starting. source
  • Check the cluster before deploying Before expecting apps to sync, run `argocd cluster get in-cluster` or run `argocd cluster get` with your cluster server URL to confirm the cluster is listed and reachable. If the cluster connection is missing or wrong, Argo CD cannot deploy or update your workloads. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why do I see 'token not valid' when using the Argo Workflows UI or API?

This can happen if Argo Server authentication is not configured correctly. If you want SSO, run with --auth-mode=sso. If you use --auth-mode=client, put Bearer in front of the ServiceAccount Secret.

Why does a workflow hang after starting?

Check the wait container logs for RBAC errors.

Where can I ask questions or get community help for Argo Workflows?

You can use the GitHub Discussions forum to discuss code, ask questions, and collaborate with the developer community.

Answers sourced from argo-workflows.readthedocs.io, argo-workflows.readthedocs.io, github.com

Community

Collected 48 days ago - public community threads