earthly/earthlyimage requires that it is run as
--privileged, if it is meant to be used with the embedded BuiltKit daemon. This is mainly due to the use of overlayfs and the internal networking setup.
earthly/earthlyimage is used with a pinned version when used in the context of a CI, in order to avoid accidental future breakage as
/usr/bin/earthly-entrypoint.shas the entrypoint
earthly/earthlyimage comes with an entrypoint that first starts up BuildKit and then issues an
earthlycommand that makes use of it. You may use the image just as you would use
earthlyitself otherwise. Any arguments are passed into the
earthly/earthlyimage in conjunction with a remote BuildKit Daemon. You may use the environment variable
BUILDKIT_HOSTto specify the hostname of the remote BuildKit Daemon. When this environment variable is set, the
earthly/earthlyimage will not attempt to start BuildKit and will instead use the remote BuildKit Daemon.
/workspace). You will need to copy or mount the necessary files to that directory prior to invoking the entrypoint.
--ciflag disables output by default. In such circumstances, you can use the
NO_DOCKERenvironment variable to disable checking for the presence of Docker. This will disable some warnings that would otherwise be printed to the console as Earthly starts up.
/tmp/earthlyas a Docker volume results in the following error: