earthly/buildkitd. This guide is intended to help you identify if you might benefit from this configuration, and to help you set it up correctly.
dockerdis missing, or you lack sufficient privileges, or it is simply not powerful enough)
8371-8373to communicate, so these should be open and available.
earthly/buildkitddaemon as a remotely available daemon, you will need to start the container yourself. See our configuration docs for more details on all the options available; but here are the ones you need to know:
buildkitdto listen on port
8372. If you would like it to be externally available on a different port, you will need to handle that at the port mapping level. TCP is required for remotely sharing a daemon.
truefor all daemons that will handle production workloads. This daemon by design is an arbitrary code execution machine, and running it without any kind of mTLS configuration is not recommended.
earthly/buildkitddaemon. However, when relying on a remote
earthly/buildkitdinstance, Earthly will not attempt to manage this daemon. Here are the configuration options needed to use a remote instance:
tcp://my-cool-remote-daemon:8372. If the hostname is considered to be a "local" one, Earthly will fall back to the Local-Remote behaviors described below. For reference; all IPv6 Loopback addresses,
[localhost](http://localhost)are considered to be "local". The machine's hostname is not considered "local".
~/.earthly/config.yaml, unless absolute paths are specified.
truewhen using TLS is desired.
tcp://127.0.0.1:8372. This is a great way to test some of the remote capabilities without having to generate certificates or manage a separate machine.