RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/dotnet/aspire/issues/6830 below:

Dev Container with `docker-outside-of-docker` never gets healthy emulated resource · Issue #6830 · dotnet/aspire · GitHub

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

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4