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
I did not see daprio/dapr:latest and redis containers. Below is what I saw.
PS C:\dapr> dapr init
Making the jump to hyperspace... Downloading binaries and setting up components... Success! Dapr is up and running
PS C:\dapr> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
After I switch Docker Desktop to use Linux containers, I was able to see the two containers running after 'dapr init'.
Steps to Reproduce the Problem
Set Docker Desktop to use Windows container and then run 'dapr init'.
The text was updated successfully, but these errors were encountered:
Expected Behavior
Following the instructions in https://github.com/dapr/docs/blob/master/getting-started/environment-setup.md for Windows, after running "dapr init", I expect to see daprio/dapr:latest and redis container images running.
Actual Behavior
I did not see daprio/dapr:latest and redis containers. Below is what I saw.
PS C:\dapr> dapr init
Making the jump to hyperspace... Downloading binaries and setting up components... Success! Dapr is up and running
PS C:\dapr> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
After I switch Docker Desktop to use Linux containers, I was able to see the two containers running after 'dapr init'.
Steps to Reproduce the Problem
Set Docker Desktop to use Windows container and then run 'dapr init'.
The text was updated successfully, but these errors were encountered: