Aspire.Hosting.Dcp.dcpctrl.ContainerReconciler[0] : could not detach network from the container

[Yzy-pg]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

M1 Pro, Aspire program cannot start when creating containers in Dockers. What is the reason for this? The error message is a network problem. Did you use a none type network?

fo: Aspire.Hosting.DistributedApplication[0]
Aspire version: 9.0.0+01ed51919f8df692ececce51048a140615dc759d
info: Aspire.Hosting.DistributedApplication[0]
Distributed application starting.
info: Aspire.Hosting.DistributedApplication[0]
Application host directory is: /Users/y/RiderProjects/clean-architecture/AppHost
info: Aspire.Hosting.DistributedApplication[0]
Now listening on: http://localhost:15210
info: Aspire.Hosting.DistributedApplication[0]
Login to the dashboard at http://localhost:15210/login?t=90090534-1cf5-4e71-86e7-9cc99f2392c1
info: Aspire.Hosting.DistributedApplication[0]
Distributed application started. Press Ctrl+C to shut down.
fail: Aspire.Hosting.Dcp.dcpctrl.ContainerReconciler[0]
could not detach network from the container {"Container": {"name":"cache-tqmvdbuy"}, "Reconciliation": 3, "ContainerID": "e8fe3c49e4868a3de1d43de4cda1c2e2dafdb570343375376c8f8c498cb08f26", "Network": "", "error": "docker command 'DisconnectNetwork' returned with non-zero exit code 1: command output: Stdout: '' Stderr: 'Error response from daemon: page not found\n'"}

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

.NET 8.0

Anything else?

No response

[SurtonYu]

My problem, like yours, has not been solved yet

[SurtonYu]

According to the guidance, the container network was checked and the disconnect command was manually executed, but the error still persists

[karolz-ms]

From the error message looks like the network ID for the detach operation is empty. This should not happen. My guess: we are inspecting the container right after creation and it is not connected to the bridge network yet. @danegsta have you seen this?

[SurtonYu]

Thank you sir, this issue has been resolved. I used version 8.0.2 and upgraded to version 9.0.0 without encountering this problem

[Hygge]

thank you，It turns out the version is causing the problem

[Yzy-pg]

@OceanYuss @karolz-ms Thank you, after I upgraded the version, it is now working properly