Im not sure is this still relevant because of the https://github.com/dotnet/aspire/issues/4461 But I have found a strange (actually not, but it took some hour to figure out) behaviour with DataVolumes in Aspire, especially when you doing with a lot of "playgrounds or versions of a repositories for projects"

So, here it is: if a data volume was already created with some "password" and then you introduce new password through the aspire API like a parameter. Then Aspire does its job and passes new cstring everywhere, but you would have "incorrect password" problems.

Solution - rename the volume by providing the string with a data volume name

As of solution

p.s. My first answer here, sorry if it does not solve your problem