Integrating Earthly into your CI is simply a matter of automating the same steps you would use for your local installation. In this guide, we will walk through this process.
The first step is to ensure that Earthly's pre-requisites, Docker and Git, are available. On many CI systems both of these already exist in the default base image or environment. Refer to your provider's documentation.
Vendors known to include these dependencies:
docker:git with service
Azure DevOps vmImage
AWS CodeBuild image
In addition to Docker and Git, Earthly also requires privileged mode as it executes container builds under the hood. In most linux-based CI environments, this is readily available and no special setting is necessary. GitLab CI requires using a compatible runner (eg Docker) and explicitly enabling privileged mode.
The next step is to install the
earthly command. For this, you need to run the command:
sudo /bin/sh -c 'wget https://github.com/earthly/earthly/releases/download/v0.5.17/earthly-linux-amd64 -O /usr/local/bin/earthly && chmod +x /usr/local/bin/earthly'
In certain CI environments, such as Jenkins, where you have access to the host, it may be more convenient to install Earthly on the host in advance, so that your builds do not need to download
earthly every time they run.
Depending on your needs, you may need to ensure that Git has authenticated access and / or that Docker is logged in so that it has access to private repositories.
To authenticate Git, you may either use SSH-based authentication, or username-password-based authentication. See the Authentication page for more information. If no authentication is configured,
earthly will fall back to using public https access.
To log in Docker, simply run
docker login --username '<username>' --password '<password>'
earthly automatically detects the presence of a TTY for the purpose of deciding whether to use colorized output or not. In some CI environments, this kind of detection is not enough in order to infer support for colorized output. However, two environment variables can be used to either disable or force it:
NO_COLOR=1 disables the use of color.
FORCE_COLOR=1 forces the use of color.
The following environments are known to require additional settings:
GitHub Actions: requires
If you would like to enable pushing Docker images to registries and also running
RUN --push commands, you might use
earthly --push +target-name
If you need to pass secrets to the Earthly build, you might also use the
--secret flag, mentioning the env var where the secret is kept.
earthly --secret SOME_SECRET_ENV_VAR +target-name
For more information see the earthly command reference.
A couple of build examples are available for