RunAsDocker

[tjwald]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

We are trying in our inner dev loop to run the services 99% of the time as native processes for fast cycles.

However, we do want every now and then to test the service using the docker image in aspire.

Currently there is no easy way to do this without breaking type safety.

Describe the solution you'd like

I would like an extension method for python, typescript and any service with a dockerfile configured to be able to run as docker.

We can then have this behind an envvar / feature flag to turn off or on. But we need the primitive in the framework

Additional context

We want this locally, but also in integration tests we would want to run using docker and not using the native process.

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• Support running and debugging Aspire service projects in Containers #969
• Feature Request: Run project as container during dotnet run in Aspire (dev‑time, not publish‑time) #11075

[afscrome]

I have been doing the opposite (replacing a container with a project) - #8984 (comment)

The main reason I went that way is that we're sharing our integrations around as nuget packages, so it's easier to have the nuget package focus on container only, and then specific consumers can substitute a project in place of a container. But I imagine you could do a similar thing to substitute a container in place of a project (executable) resource.

The core support is there already - you simply need to add a ContainerImageAnnotation to the resource, and dcp will run it as a containers. However adding this annoation to an executable get into a state where dcp tries to run your resource as both an executable and project, which horribly confuses dcp.

[tjwald]

@karolz-ms this is not dotnet project specific and doesn't have to deal with debugging containers.
We want to be able to choose to run as either native executable or container of any executable not just dotnet.
Why did you mark this as duplicate?

[karolz-ms]

Fair enough--this covers more than just .NET. For .NET-based services #969 is pretty much identical, that is why I initially resolved this issue as a duplicate.

[afscrome]

You can also look at the various RunAsContainer or RunAsEmulator methods on Azure resources which convert an Azure resource into a container resource. Although I think you'll hit the same problem that whilst you can add the container bits to the project, you can't remove the executable bits, so DCP will start the resource as both an executable and a container.