Zarf fails local 'docker' fallback with docker-over-ssh

[mjnagel]

Environment

Device and OS: macOS, with Ubuntu over SSH App version: 0.38.3 Kubernetes distro being used: N/A

Steps to reproduce

1. Setup docker daemon on a remote box that you can SSH to (this tutorial may be helpful).
2. Set your docker host to be the remote docker-over-ssh. Note that this must be done via the DOCKER_HOST env due to this issue. For example: export DOCKER_HOST=ssh://[email protected].
3. Test some docker commands, validate connection works (could also validate with k3d and other tooling that interacts with the docker daemon).
4. Attempt to build a zarf package that requires the local docker fallback.

Expected result

Zarf is able to pull the image from "local" docker daemon (or fails to find the image).

Actual Result

Zarf fails to connect, appearing to try and hit the docker endpoint with an http call.

Visual Proof (screenshots, videos, text, etc)

 WARNING  Falling back to local 'docker', failed to find the manifest on a remote: GET
          https://index.docker.io/v2/mjnagel/test123/manifests/latest: MANIFEST_UNKNOWN: manifest
          unknown; unknown tag=latest
     ERROR:  failed to create package: error during connect: Get "http://mjnagel%401.2.3.4/v1.24/images/docker.io/mjnagel/test123:latest/json": dial tcp: lookup [email protected]: no such host

Severity/Priority

Medium - no known workarounds for this outside of being directly on the box with the docker daemon.

Additional Context

Unsure if this is a bug or just a known limitation.