Chainloop is comprised of two main components
- A Server Side Component (Control Plane + Artifact Storage Proxy) that acts as single source of truth and management console.
- A Command Line Interface (CLI) used to both a) operate on the control plane and b) run the attestation process on your CI/CD
Command Line Interface (CLI) installation
To install the latest version for macOS, Linux or Windows (using WSL) just choose one of the following installation method.
- Installation Script
- GitHub Release
- From Source
curl -sfL https://docs.chainloop.dev/install.sh | bash -s
you can retrieve a specific version with
curl -sfL https://docs.chainloop.dev/install.sh | bash -s -- --version v0.1.2
and customize the install path (default to /usr/local/bin)
curl -sfL https://docs.chainloop.dev/install.sh | bash -s -- --path /my-path
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
curl -sfL https://docs.chainloop.dev/install.sh | bash -s -- --force-verification
Refer to GitHub releases page and download the binary of your choice.
git clone firstname.lastname@example.org:chainloop-dev/chainloop
cd chainloop && make -C app/cli build
=> chainloop version v0.8.93-3-ged05b96
Deploy Chainloop (optional)
Downloading the CLI is everything you need to give Chainloop a try since, by default, it points to a running instance of Chainloop.
To run a Chainloop instance on your Kubernetes cluster follow these instructions.
Configure CLI (optional)
If you are running your own instance of Chainloop Control Plane. You can make the CLI point to your instance by using the
chainloop config save command.
chainloop config save \
--control-plane my-controlplane.acme.com \
Another option would be to build a custom version of CLI with default endpoints' values pointing at your Chainloop instance. Please learn more about this method in the following doc.
Authenticate to the Control Plane by running
$ chainloop auth login
Welcome to Chainloop!