Alex Couture-Beil

this looks cool! I wonder if `/var/lib/docker/volumes/earthly-cache` could be backed without the use of a `docker run`? I've never looked into if it's possible.

it looks like it's used when deciding to save to the cache under https://github.com/earthly/actions-setup/blob/b61ca413d8100e151c4e517e433a617a402f5051/src/cache-save.ts#L34-L37 maybe something similar can be done under https://github.com/earthly/actions-setup/blob/b61ca413d8100e151c4e517e433a617a402f5051/src/cache-restore.ts#L8 ? PRs are most welcomed :)

I agree that it feels like a bug. We haven't had a chance to look into a fix for this; I'm unsure how much effort is required. We would gladly...

Thanks for the ideas. There's a bit of overlap with #607; I wonder if earthly supported a `--keep-going` flag, would that in addition to a `TRY` / `FINALLY` (once it...

unfortunately there's been no progress on `--keep-going`; it sounds straight-forward; however it requires significant modifications to the buildkit codebase, which would bring our fork even further away from upstream buildkit.

This issue stems from buildkitd running out of a seperate container that does use the host's network resolver (or `/etc/hosts` file). e.g. `docker exec earthly-buildkitd /bin/sh -c 'cat /etc/hosts'` will...

does it work with the IP address instead? unfortunately this isn't a trivial fix.

I wonder if the `common` step was getting garbage-collected between the individual `earthly` calls?

Thanks for reporting this, I suspect we need to add in: ``` docker network ls --filter 'type=custom' -q | xargs -r docker network rm --force ``` somewhere in https://github.com/earthly/earthly/blob/11c9b045ef186249de7ff952394edeca0f2f12f8/buildkitd/dockerd-wrapper.sh#L114

It's hard to completely understand the issue -- can you give a minimal example that can be run, along with the output.