buildkitwith some Earthly-specific setup. This is what Earthly will start when using a local daemon. You can also start it up yourself and use it as a remote/shared BuildKit daemon.
earthly. Mismatched versions are unsupported.
docker runcommands that cover the most common use-cases:
--privilegedis required. This is because
earthlyneeds some privileged
-ttells Docker to emulate a TTY. This makes the
buildkitlog output colorized.
-v earthly-tmp:/tmp/earthly:rwmounts (and creates, if necessary) the
earthly-tmpDocker volume into the containers
/tmp/earthly. This is used as a temporary/working directory for
EARTHLY_BUILDKIT_HOST=docker-container://<container-name>, or by specifying the appropriate values in
buildkitdlisten on a TCP port instead of a Unix socket.
-p 8372:8372forwards the hosts port 8372 to the containers port 8372. When using TCP,
buildkitwill always listen on 8372, but you can configure the apparent port by forwarding a different port on your host.
fast-builder, you could use this remote
EARTHLY_BUILDKIT_HOST=tcp://fast-builder:8372, or by specifying the address in your
buildkitdneeds appropriate access to start and run additional containers itself via
buildkitdcan consume excessive disk space and/or operate very slowly.
earthly, please note that setting
EARTHLY_BUILDKIT_HOSTvalues with hosts
localhostare considered local and will result in Earthly attempting to manage the BuildKit container itself. Consider using your hostname, or another alternative name in these cases.