Skip to main content

Installation

LaraKube CLI is designed for speed and stability. You can get up and running with a single command, or choose a manual installation if you prefer more control.

The fastest way to install LaraKube CLI is using our automated installer. This will download the latest standalone binary for your architecture, install it globally, and initialize your configuration.

curl -fsSL https://cli.larakube.app/install.sh | bash

🔐 Note: The installer will ask for your sudo password to move the binary into your global /usr/local/bin directory.

Installing a canary build​

Canary is the tip of develop, republished on every push. Use it when you need a fix or feature that has not reached a tagged release yet — it is unstable by definition and may be broken.

curl -fsSL https://cli.larakube.app/install.sh | bash -s -- --canary

The installer puts canary at /usr/local/bin/larakube, replacing a stable build already installed there. That is deliberate — --canary is an explicit choice — but it means larakube is the canary from then on, until you switch back with larakube update or re-run the installer with --stable.

This is the path to use on WSL and Linux, where Homebrew is not available. On macOS you can use Homebrew instead, which installs canary side by side with stable as a separate larakube-canary command:

brew install luchavez-technologies/larakube/larakube-canary

Once installed, move between channels at any time:

larakube update            # latest stable release
larakube update --canary   # latest canary build

A Homebrew-managed install updates through brew instead, and larakube update will say so rather than replacing the binary behind Homebrew's back.

🧭 Next: tell LaraKube CLI what this machine is for​

larakube setup

setup asks a single question, because the answer changes everything that follows:

  • Cluster Tools and remote clusters — you want to self-host chat, a wiki, single sign-on and the rest on a server you own. This installs kubectl, offers OpenTofu, and skips every local-development step. No container runtime is needed. See Cluster Tools Without a Dev Setup.
  • Local development — you want to build and run your own apps on this machine. This needs Docker, OrbStack or Podman with Kubernetes enabled. See the macOS, Linux and Windows pages.

When no container runtime is running, the first is the default. Choose without being asked with --profile=remote or --profile=local.

🔌 AI & MCP Configuration​

To unlock the full power of LaraKube CLI's AI-Native Orchestration, you should register the LaraKube CLI tools with your favorite AI host.

# Register for Gemini and Claude Desktop
larakube mcp:register --all

🏁 Verification​

Confirm your installation by checking the version and cluster status:

larakube about

🔒 Post-Installation: Trusting SSL​

To enjoy seamless HTTPS without browser warnings, you should trust the LaraKube Local CA on your host machine.

# Works on macOS, Linux, and Windows WSL2
larakube trust

You are now ready — install your first Cluster Tool or build your first app. 🚀🍭🕺🐘