Sql Server container port is not accessible after Aspire is shutdown

[christophe-mommer]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm using Aspire to orchestrate my webapp and my database. I'm also using this database as part of several other projects, like test project.
Here's my setup:

var password = builder.AddParameter("sqlpassword", secret: true);
var sqlServer = builder
    .AddSqlServer(ConfigurationConstants.SqlServerConnectionName, password, 1433)
    .WithLifetime(ContainerLifetime.Persistent)
    .WithDataVolume(name: ConfigurationConstants.SqlServerDataVolumeName, isReadOnly: false)
    .WithContainerName("sql-server");

var sqlDatabase = sqlServer.AddDatabase(ConfigurationConstants.SqlDatabaseConnectionName);

webFrontEnd
    .WithReference(sqlDatabase)
    .WaitFor(sqlDatabase);

The thing is: when my Aspire app si running, I can access the database on port 1433 from other applications, even SSMS. However, when I shutdown my Aspire project, this database is no more accessible, even though it's marked as persistent. The container is still there, but the random port is the only one that allows me to acces the database, not the 1433 that I've specified.

Have I missed something in my configuration?

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

.NET 9, Aspire 9

Anything else?

No response

[maddymontaquila]

cc @danegsta

[maddymontaquila]

@lupusbytes quick fyi - when using ContainerLifetime.Persistent it does stay running when Aspire shuts down - you can tell because in Docker Desktop it still shows it as "running", so yeah this is a bug 😁

[karolz-ms]

My guess here is that AddSqlServer() () is using proxied endpoint for a persistent container, and once the app host stops, the proxy is gone, and the port specified is no longer valid. As a rule, it probably does not make sense to use proxied endpoints for persistent containers.

So If that is correct, it is not a feature, but just a bug in the app model.

[karolz-ms]

Actually, the feature that we might be missing is "change the type of the endpoint depending on whether the container is persistent"

[garrettlondon1]

Can confirm as well, not able to connect to local sql server database running in docker container via Azure Data Studio without aspire running.

[davidfowl]

Actually, the feature that we might be missing is "change the type of the endpoint depending on whether the container is persistent"

We should just do this automatically right?

[karolz-ms]

Actually, the feature that we might be missing is "change the type of the endpoint depending on whether the container is persistent"

We should just do this automatically right?

@danegsta is working on making non-proxied endpoints the default for persistent containers.

[danegsta]

We just merged #7232 which adds a new .WithEndpointProxySupport experimental API for container resources. Specifying .WithEndpointProxySupport(false) will disable proxying on all endpoints for a given resource. It's highly recommended to set explicit host ports for your container resources to avoid potential port conflicts as the default behavior for un-proxied container endpoints is to expose the endpoint using the internal port for the container.

We made the new API experimental and opt-in because there's additional larger work that will need to happen to unblock enabling the behavior by default, but we wanted to still provide a straightforward workaround in the short term. You can try out the API in nightly builds or the upcoming 9.1 release.