Install ArgoCD on Fedora 41: Complete Guide (2026)

Here is how to install the ArgoCD CLI on Fedora 41. Tested and verified.

Scope: This guide installs the argocd command-line client only — a single static binary with no daemon, no systemd service, and no dedicated system group. The ArgoCD server runs as pods inside a Kubernetes cluster. If you don’t already have one running, see Install ArgoCD on Kubernetes or Install ArgoCD on K3s first.

Prerequisites

• Fedora 41 installed and updated
• Root or sudo access
• Internet connection
• An existing ArgoCD server to log into (optional to install the CLI itself, required to actually use it)

Step 1: Update System

sudo dnf update

Step 2: Detect Your Architecture and Download the CLI Binary

The ArgoCD CLI has no dnf package and no official RPM repository — the project does not publish one. The supported installation method is downloading the prebuilt static binary for your CPU architecture directly from the ArgoCD GitHub releases page. This step is identical across every Linux distribution; there is nothing Fedora-specific about it.

# Ensure curl is available
sudo dnf install -y curl

# Detect CPU architecture (x86_64 -> amd64, aarch64 -> arm64)
case "$(uname -m)" in
  x86_64)  ARGOCD_ARCH="amd64" ;;
  aarch64) ARGOCD_ARCH="arm64" ;;
  *) echo "Unsupported architecture: $(uname -m)" >&2; exit 1 ;;
esac

# Download the matching binary
curl -sSL -o argocd-linux-$ARGOCD_ARCH "https://github.com/argoproj/argo-cd/releases/latest/download/argocd-linux-$ARGOCD_ARCH"

Step 3: Install the Binary

sudo install -m 555 argocd-linux-$ARGOCD_ARCH /usr/local/bin/argocd
rm argocd-linux-$ARGOCD_ARCH

Step 4: Verify Installation

argocd version --client

Expected output shows only the client version — there is no local server for it to compare against.

Step 5: Shell Completion and Connecting to a Server

Optional: enable bash completion for the argocd command.

argocd completion bash | sudo tee /etc/bash_completion.d/argocd > /dev/null

The binary alone doesn’t do anything until it’s pointed at a running ArgoCD server:

argocd login <your-argocd-server>:443

If you don’t have a server yet, deploy one first: Install ArgoCD on Kubernetes or Install ArgoCD on K3s.

Troubleshooting

command not found: argocd

/usr/local/bin isn’t on every shell’s PATH by default. Confirm it’s included, or open a new shell session:

echo $PATH | tr ':' '\n' | grep /usr/local/bin
which argocd

Binary Won’t Run / Permission Denied

If you copied the binary manually instead of using install -m 555, it may not be marked executable:

sudo chmod +x /usr/local/bin/argocd

x509: certificate signed by unknown authority

This happens when argocd login connects to a server presenting a self-signed certificate. For a lab or test server, skip verification:

argocd login <your-argocd-server>:443 --insecure

For production, import the server’s CA certificate into your trust store instead of using --insecure.

Uninstall

The CLI is a single file, not something installed through a package manager — remove it directly:

sudo rm /usr/local/bin/argocd

Related Guides

• Install ArgoCD on Kubernetes
• Install ArgoCD on K3s
• ArgoCD Cheat Sheet
• ArgoCD Tutorial
• Docker vs Kubernetes

About the Author

I am Luca Berton, AI and Cloud Advisor. Book a consultation to get help with your infrastructure setup.