Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AzureTools][Aspire] The corresponding container in the Dashboard restart failed with an error when restarting the running container in Docker Desktop #6782

Open
v-mengwe opened this issue Nov 25, 2024 · 1 comment
Assignees
Milestone

Comments

@v-mengwe
Copy link

v-mengwe commented Nov 25, 2024

REGRESSION INFO: Not a regression, this issue also reproduces on Aspire 9.0.0 and it is unstable on Aspire 9.0.0.

Clean machine: Win11 x64 23h2 ENU
VS Version: VS 17.13.0 Preview 2.0 [35523.93.main]
Aspire Version: 9.1.0-preview.1.24574.1
Apply NuGet Feeds
Docker Desktop: 4.36.0

Repro Steps:

  1. Create an Aspire starter project with "Use Redis for caching (requires Docker)" checked. -> F5.
  2. Restart the running container in Docker Desktop.
  3. Check whether the state of the corresponding container in the dashboard changes accordingly.

Expect:
The corresponding container in the Dashboard restarts successfully without any error.

Actual:
The corresponding container in the Dashboard restart failed with an error.
Image

More Info:
The state of the corresponding container in the dashboard does not change with it when restarting the conatiner in the Podman Desktop.

@dbreshears
Copy link
Contributor

Host port is changing and we are not rebinding the proxies, thus the container shows unhealthly. Quick workaround is to restart from the dashboard or go proxyless. Should be able to detect this restart event and update ports.

@dbreshears dbreshears modified the milestones: Backlog, 9.2 Feb 12, 2025
@dbreshears dbreshears self-assigned this Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants