Earthly has the ability to use secure cloud-based storage for build secrets. This page goes through the basic setup and usage examples.
Cloud secrets can be used to share secrets between team members or across multiple computers and a CI systems.
This document covers the use of cloud-hosted secrets. It builds upon the understanding of build arguments and locally-supplied secrets.
In order to be able to use cloud secrets, you need to first register an Earthly cloud account.
earthly account register --email <email>
An email will be sent to you containing a verification token, next run:
earthly account register --email <email> --token <token>
This command will prompt you to set a password, and to optionally register a public-key for password-less authentication.
It is recommended that you register a public RSA key during registration; if this is done, you will be logged in automatically whenever earthly needs to authenticate you. If you did not supply a public key, then your plain-text password will be cached on your local disk under
~/.earthly/auth-token, which will be used to log you in. If this file is deleted, you will need to run
earthly account login to re-create it.
To logout, you can run
earthly account logout, which deletes the
~/.earthly/auth-token file from your disk.
Each user has a non-sharable private userspace which can be referenced by
/user/...; this can be thought of as your home directory. To view this workspace, try running:
earthly secrets lsearthly secrets ls /user
Secrets are referenced by a path, and can contain up to 512 bytes.
To set a secret value, use the
secrets set command:
earthly secrets set /user/my_key 'hello world'
To view a secret value, use the
secrets get command:
earthly secrets ls /userearthly secrets get /user/my_key
Cloud secrets can be referenced in an Earthfile, in a similar way to locally-defined secrets.
Consider the Earthfile:
FROM alpine:latestbuild:RUN --secret MY_KEY=+secrets/user/my_key echo $MY_KEYSAVE IMAGE myimage:latest
The env variable
MY_KEY will be set with the value stored under your private
You can build it via:
To share secrets between teams, an organization must first be created:
earthly org create <org-name>
Then additional users can be invited into the organization:
earthly org invite /<org-name>/ <email>
By default this will grant the invited user read privileges to all keys under the organization. It's also possible to use the
--write flag to grant write permission too. Additionally, the permissions can be set to lower paths.
earthly account register --email [email protected] --token ...earthly account register --email [email protected] --token ...
Alice then creates an organization called hush-co:
earthly org create hush-co
Alice then creates a secret under the
project-zulu sub directory:
earthly secrets set /hush-co/project-zulu/transponder-code peanut
Alice then grants Bob read permission on all of
earthly org invite /hush-co/project-zulu/ [email protected]
Bob now has permission to everything under the
/hush-co/project-zulu/ directory. If he runs
earthly secrets ls /hush-co/
he will see:
However if Alice were to create any secrets outside of
project-zulu, Bob would not be able to list or retrieve them.
To reference secrets from a CI environment, you can make use of the password or ssh-key authentication referenced under the login/logout section, or you can generate an authentication token by running:
earthly account create-token [--write] <token-name>
This token can then be exported as
Which will then force Earthly to use that token when accessing secrets. This is useful for cases where running an ssh-agent is impractical.
The Earthly command uses HTTPS to communicate with the cloud secrets server. The server encrypts all secrets using OpenPGP's implementation of AES256 before storing it in a database. We use industry-standard security practices for managing our encryption keys in the cloud.
Secrets are presented to buildkit in a similar fashion as locally-supplied secrets: When buildkit encounters a
RUN command that requires a secret, the buildkit daemon will request the secret from the earthly command-line process --
earthly will then make a request to earthly's cloud storage server (along with the auth token); once the server returns the secret, that secret will be passed to buildkit.
The secrets store is still an experimental feature, we would love to hear feedback in our Slack community.