Skip to main content
Version: 1.9.0

Installation of the Epinio CLI

The epinio cli can be used to interact with a cluster that has Epinio installed on it. Application developers shouldn't need to access the cluster directly. Requests to the Epinio API server are authenticated with Basic Auth. No direct access to the cluster is required (e.g. through kubectl).

From Homebrew (Linux and Mac)​

Epinio has its own formula available in the homebrew/core tap.

brew install epinio

Alternatively, if you want to get the latest Epinio CLI faster, there is a custom tap you can use:

brew tap epinio/tap
brew install epinio/tap/epinio

From the Binary Releases​

Find the latest version at Releases.


curl -o epinio -L


curl -o epinio -L


 curl -LO

Extract the zip archive and put the binary in a directory that is in your PATH environment variable. Instructions on how to add directories to the PATH vary depending on your version of Windows.

Make the Binary Executable (Linux and Mac)​

chmod +x epinio

Move the binary to your PATH

sudo mv ./epinio /usr/local/bin/epinio

Verify Downloaded Files​

This is done using the cosign tool. The following commands were tested using cosign version 2.1.1.

Verify File Checksum Signature​

Instead of signing all release assets, Epinio signs a checksums file containing the different release assets checksums. You can download/copy the three files 'epinio_1.9.0_checksums.txt.pem', 'epinio_1.9.0_checksums.txt.sig', 'epinio_1.9.0_checksums.txt' from the latest release.

curl -LO
curl -LO
curl -LO

Once you have the three files locally, you can execute the following command

cosign verify-blob \
--certificate-identity-regexp "" \
--certificate-oidc-issuer "" \
--cert epinio_1.9.0_checksums.txt.pem \
--signature epinio_1.9.0_checksums.txt.sig \

A successful output looks like

Verified OK

Now you can verify the assets checksum integrity.

Verify File Checksum Integrity​

Before verifying the file integrity, you should first verify the checksum file signature. Once you’ve download both the checksums and your binary, you can verify the integrity of your file by running:

sha256sum --ignore-missing -c epinio_1.9.0_checksums.txt

For this check to be effective it is necessary that the local epinio binary has the proper name as listed in the checksum file, i.e. epinio-linux-x86_64, epinio-darwin-x86_64, etc.

For windows the checksum is for the zip archive, not for the binary inside.

Verify the Installation

Run e.g. epinio version to test the successful installation.

> epinio version
Epinio Version: v1.9.0
Go Version: go1.20