Part 7: Using remote runners
Earthly has the ability to run builds both locally and remotely. In this section, we will explore how to use remote runners to perform builds on remote machines.
Earthly is able to use remote runners for performing builds on remote machines. When Earthly uses a remote runner, the inputs of the build are picked up from the local environment, then the execution takes place remotely, including any pushes (
RUN --pushcommands, and
SAVE IMAGE --pushcommands), but any local outputs are sent back to the local environment. All this takes place while your local Earthly process still provides the logs of the build in real time locally.
Remote runners are especially useful in a few specific circumstances:
- You want to reuse cache between CI runs to dramatically speed up builds (more on this in part 8).
- You want to share compute and cache with coworkers and/or with the CI.
- You have a build that requires a lot of resources, and you want to run it on a machine with more resources than your local machine.
- You have a build that requires running on a specific CPU architecture natively.
- You have a slow internet connection.
There are two types of remote runners:
Earthly Satellites are remote runners managed by the Earthly team.
Then, you can select the org that you are part of, and create a satellite.
earthly org select <my-org>
earthly sat launch my-satellite
Once a satellite has been launched it is automatically selected for use. If you ever need to switch the satellite yourself, you can use the command...
earthly sat select my-satellite
Additionally, you can go back to performing local builds with the command...
earthly sat unselect
And then run Earthly builds as usual.
Or, you can use a satellite as part of the build without selecting first
earthly --sat my-satellite +my-target
When running remote builds, some operations might require access to secrets. For example, if you are pushing images to a private registry, or if you are logged in to DockerHub to prevent rate limiting. Earthly will automatically pass the credentials from your local machine to the remote runner.
Any secret that is available locally, including Docker/Podman credentials, will be passed to the remote runner whenever needed by the build.