You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Folks might have turned off their Docker Daemon and tried to start the Aspire App Host with container integrations, leading to a "quiet" failure. Only after going to the Services window do folks see the failure in the output.
To Reproduce
Steps to reproduce the behavior:
Turn off Docker Daemon
Attempt to start the AppHost run configuration
Quiet failure
See error
Expected behavior
Expect Rider to notify me/check that the Docker Daemon is required and not running. There are several options for UI/UX here.
Wait for a fail message in the output and report that to users
Check the Docker Daemon before running the run configuration
Screenshots
The text was updated successfully, but these errors were encountered:
I'm not sure about this. Tbh, DCP doesn't give us any information about containers, only about .NET projects. Obviously we can parse the source code and build the same model ourselves, but that might take a lot of work. Also, we can't always tell if Docker daemon is active or not, only if our Docker plugin is installed and connected to daemon. And, as far as I understand, IDE integration should only be responsible for .NET projects, everything else is a DCP thing.
Maybe this is an enhancement to the IntelliJ platform, allowing plugins to potentially watch for text that comes through the IO found in the run window and surface it in the form of a notification.
Describe the bug
Folks might have turned off their Docker Daemon and tried to start the Aspire App Host with container integrations, leading to a "quiet" failure. Only after going to the Services window do folks see the failure in the output.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect Rider to notify me/check that the Docker Daemon is required and not running. There are several options for UI/UX here.
fail
message in the output and report that to usersScreenshots
The text was updated successfully, but these errors were encountered: