RUN, however, is not a source, even if the command itself involves downloading content from an external location. This means that a
RUNcommand, on its own, would always be cached if it has been run under the same circumstances previously (except for the
earthly-cacheon your system. When Earthly starts for the first time, it brings up a BuildKit daemon in a Docker container, which initializes the
earthly-cachevolume. The volume is managed by Earthly's BuildKit daemon and there is a regular garbage-collection for old cache.
cache_size_mbsetting in the configuration. For example: