Skip to content

When running two AppHosts Aspire.Hosting.Dcp reports a proxy error when both AppHosts have the same .AddContainer #10534

@drdr-kr

Description

@drdr-kr

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

I have two different AppHost projects, both configured as follows

var builder = DistributedApplication.CreateBuilder(args);

var rabbitmqUserName = builder.AddParameter("rabbitmq-username", true);
var rabbitmqPassword = builder.AddParameter("rabbitmq-password", true);
var rabbitmq = builder
	.AddRabbitMQ("rabbitmq", rabbitmqUserName, rabbitmqPassword, 5273)
	.WithContainerName("shared-rabbitmq")
	.WithDataVolume("shared-rabbitmq")
	.WithManagementPlugin(15673)
	.WithLifetime(ContainerLifetime.Persistent);
builder.Build().Run();

(there are other things, but this is the bare minimum to reproduce)

Starting the first AppHost I can see everything healthy in the Aspire dashboard, and that the shared-rabbitmq container has started. After starting the second AppHost it also reports rabbitmq has healthy in the dashboard however after a few minutes it starts logging the following error in the console

fail: Aspire.Hosting.Dcp.dcpctrl.ServiceReconciler[0]
      could not start the proxy {"ServiceName": {"name":"rabbitmq-management"}, "Reconciliation": 46, "error": "could not start the proxy for the service: listen tcp [::1]:15673: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted."}

it logs this error periodically, however everything is working correctly

Expected Behavior

Not expecting to see this error.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

Dotnet 9
Aspire 9.3.1

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions