tar.gz generated from multi-arch ContainerArchiveOutputPath causes error with `docker load` on GitHub Actions

[flcdrg]

I have a GitHub Actions workflow that builds a multi arch container using this command:

dotnet publish -p RuntimeIdentifiers=\"linux-musl-x64\;linux-musl-arm64\" -p ContainerRuntimeIdentifiers=\"linux-musl-x64\;linux-musl-arm64\" --self-contained false /t:PublishContainer Verify.Cli -p ContainerArchiveOutputPath=${{ github.workspace }}/containers

I then try to load the .tar.gz image back into docker to test it, but it always fails with an error like this:

open /home/runner/setup-docker-action-d4f83c2f/data/tmp/docker-import-2746388556/blobs/json: no such file or directory

(If I don't use the docker/setup-docker-action@v4 task, then the default version of docker is used which results in a similar error)

open /var/lib/docker/tmp/docker-import-3559857801/blobs/json: no such file or directory

See https://github.com/flcdrg/Verify.Cli/actions/runs/14007278684/job/39222755711?pr=245#step:13:90 for example

I can't reproduce this problem on Windows or WSL with Docker Desktop installed. I assume it's something about Docker on native Ubuntu and the tar.gz file

The problem also does not occur if the tar.gz is not a multi-arch image.