Image not build if more than one compute environment added for a resource

[mastoj]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have added multiple compute environments just to my resources since I want to test it locally using docker compose locally without aspire and also deploy to azure.

If I have something like

  .WithComputeEnvironment(compose)
  .WithComputeEnvironment(containerApps);

where the environments are defined with

var compose = builder.AddDockerComposeEnvironment("docker-env");
var containerApps = builder.AddAzureContainerAppEnvironment("containerapp-env");

the images are not built for those resources. If I comment out one of the WithComputeXXX the image is built.

Expected Behavior

The image should always be built, it should not matter on the number of environments attached to it.

Steps To Reproduce

First add two environments:

var compose = builder.AddDockerComposeEnvironment("docker-env");
var containerApps = builder.AddAzureContainerAppEnvironment("containerapp-env");

Then add a resource using both:

someResource
  .WithComputeEnvironment(compose)
  .WithComputeEnvironment(containerApps);

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: Mac OS X
OS Version: 15.5
OS Platform: Darwin
RID: osx-arm64
Base Path: /usr/local/share/dotnet/sdk/9.0.100/

.NET workloads installed:
There are no installed workloads to display.
Configured to use loose manifests when installing new manifests.

Host:
Version: 9.0.0
Architecture: arm64
Commit: 9d5a6a9aa4

Anything else?

.NET Aspire 9.3

[davidfowl]

That's not how you'd go about testing multiple environments. You don't need to copy this verbatim but you need to switch based on something:

aspire/playground/publishers/Publishers.AppHost/Program.cs

Lines 11 to 22 in 90e55c7

	builder.Configuration.AddCommandLine(args, new Dictionary<string, string> { ["--target"] = "Deployment:Target" });
	var target = builder.Configuration["Deployment:Target"];
	var publisher = builder.ExecutionContext.PublisherName;
	IResourceBuilder<IComputeEnvironmentResource>? environment = (publisher, target) switch
	{
	("default", "kube") => builder.AddKubernetesEnvironment("env"),
	("default", "azure") => builder.AddAzureContainerAppEnvironment("env"),
	("default", _) => builder.AddDockerComposeEnvironment("env"),
	_ => null
	};

You only need WithComputeEnvironment when you are using both at the same time.

[mastoj]

thanks, make sense.

[davidfowl]

When you use aspire publish, cli arguments pass through so you can make up arguments 😄

[Was85]

I attempted to use Azure Container Apps on its own but wasn’t able to build any images. However, when I tested the Docker Compose setup, it worked exactly as expected.

`var containerApps = builder.AddAzureContainerAppEnvironment("containerapp-env");

logapi = logapi.WithComputeEnvironment(containerApps).PublishAsAzureContainerApp((infra, app) =>
{

});
webclient = webclient.WithComputeEnvironment(containerApps).PublishAsAzureContainerApp((infra, app) =>
{

});
`

[davidfowl]

For azure, use azd to publish assets and deploy for azure based apps. The support for aspire publish is not complete for azure.