Skip to main content

​
Get access to Chainloop

This guide assumes that you have access to a Chainloop Cloud account or to your own Chainloop instance of Chainloop. If you don’t, please contact us, and we’ll get back to you shortly.

​
Install the Chainloop Command Line Interface (CLI)

The Chainloop CLI is used to send pieces of evidence and attestations to the platform. During this getting started, we’ll use the CLI to perform local attestations first but later in a CI/CD system. To install the latest version for macOS, Linux or Windows (using WSL) just choose one of the following installation method. 
curl -sfL https://dl.chainloop.dev/cli/install.sh | bash -s -- --ee
you can install a specific version with
curl -sfL https://dl.chainloop.dev/cli/install.sh | bash -s -- --ee --version vx.x.x
and customize the install path (default to /usr/local/bin)
curl -sfL https://dl.chainloop.dev/cli/install.sh | bash -s -- --ee --path /my-path
To install without sudo, provide a user-accessible path:
curl -sfL https://dl.chainloop.dev/cli/install.sh | bash -s -- --ee --path ~/.local/bin
if cosign is present in your system, in addition to the checksum check, a signature verification will be performed. This behavior can be enforced via the —force-verification flag.
curl -sfL https://dl.chainloop.dev/cli/install.sh | bash -s -- --ee --force-verification

​
On-Premises CLI Configuration (if applicable)

If you are running your own instance of Chainloop Platform. You must change the default endpoints’ values pointing by using the following command: 
chainloop config save \
  --control-plane my-controlplane.acme.com:443 \
  --artifact-cas cas.acme.com:443 \
  --platform my-platform.acme.com:443