[13.1] Container Tunnel fails to start.

[darwinx95]

Is there an existing issue for this?

• Related to [13.0] Container Tunnel fails to start. #12842, which was fixed in [main] Update dependencies from microsoft/usvc-apiserver #13101
• I have searched the existing issues

Describe the bug

In 13.1.0, I am trying to start my AppHost with ASPIRE_ENABLE_CONTAINER_TUNNEL set as true in launch settings, causing the App Host to hang before the dashboard shows up.

Running Podman instead of Docker, with docker compatibilty..

Expected Behavior

1. Tunnel to start, AppHost to start aswell
2. Dashboard to load

Steps To Reproduce

No response

Exceptions (if any)

Waiting for container network 'aspire-container-network' tunnel initialization...
dbug: Aspire.Hosting.Dcp.dcpctrl.dcpctrl.NetworkReconciler[
  0
]
      Network created   {
  "ContainerNetwork": "/aspire-container-network",
  "Reconciliation": 2,
  "NetworkName": "aspire-session-network-hahmuarb-Aspire"
}
dbug: Aspire.Hosting.Dcp.dcpctrl.dcpctrl.TunnelProxyReconciler[
  0
]
Container image check for container network tunnel could not be queued    {
  "ContainerNetworkTunnelProxy": "/aspire-container-network-tunnelproxy",
  "Reconciliation": 5,
  "error": "failed to build client proxy image: podman command 'BuildImage' returned with non-zero exit code 125: command output: Stdout: '' Stderr: 'Error: reading build instructions: open /mnt/c/Users/<user>/AppData/Local/Temp/aspire-dcphkha5ok3.hzj/dcptun-build-1305609021/Dockerfile: permission denied\n\n'"
}

.NET Version info

No response

Anything else?

No response

[davidfowl]

What version of podman?

[darwinx95]

I am using podman desktop v1.23.1

[davidfowl]

What version of podman itself ? Run podman version

[darwinx95]

Podman is version 5.7.1

[danegsta]

There’s an issue with the tunnel when combined with an endpoint running unproxied that causes it to hang.

[darwinx95]

Edited initial issue logs, there was some more information that I hadn't included.
Looking at the temp folder mentioned in the error, I only see a kubeconfig and output.sock in the initial folder (aspire-dcphkha5ok3.hzj), the folder it mentions does not exist, which means the dockerfile also doesn't exist..