Dev Container with `docker-outside-of-docker` never gets healthy emulated resource

[erwinkramer]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When running Aspire inside a Dev Container with docker-outside-of-docker feature instead of docker-in-docker, the resource (for instance an emulated blob storage), never gets a healthy status and is not usable.

I see that the container does start in the host docker desktop (in my case), and no other errors seem to be popping up.

Expected Behavior

The resource should get a healthy status and be usable.

Steps To Reproduce

• Use docker desktop inside your host.
• Clone https://github.com/erwinkramer/bank-api
• Modify the devcontainer.json to use docker-outside-of-docker instead of docker-in-docker
• Run the dev container.
• Start the launch config C#: App Host Debug (via Aspire).

Exceptions (if any)

No response

.NET Version info

.NET SDK:
Version: 9.0.100
Commit: 59db016f11
Workload version: 9.0.100-manifests.3068a692
MSBuild version: 17.12.7+5b8665660

Runtime Environment:
OS Name: debian
OS Version: 12
OS Platform: Linux
RID: linux-x64
Base Path: /usr/share/dotnet/sdk/9.0.100/

Anything else?

No response

[mitchdenny]

Docker outside of Docker is effectively a remote docker scenario for dev containers and .NET Aspire does not currently support working against a Docker daemon on a remote machine. When using devcontainers you need to use docker-in-docker.

We have added improved support for devcontainers in .NET Aspire 9.1, you can checkout our Devcontainer template here: https://github.com/dotnet/aspire-devcontainer (still needs a few updates once we ship the 9.1 nuget packages).

Looks like you've got the devcontainer in your repro set for docker-in-docker now anyway...