Summary
The user is building a Docker image using Gitea Actions on a virtual machine and encounters an issue where Earthly tries to use Docker over the network instead of the Unix socket. They provided their CI configuration, which includes steps for installing Earthly, logging into Docker and GitHub Container Registry, and executing a sample command. However, the final step fails with a "connection refused" error when pulling the Docker image. The user clarified that the problem is related to the pull ping mechanism connecting to the Earthly Buildkit daemon, not using Docker over the network. A suggested solution was to set EARTHLY_DISABLE_REMOTE_REGISTRY_PROXY=1 to switch to a tar-based export mechanism, which resolved the issue.