search

dotnet / tye

Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.
MIT License
5.29k stars 520 forks source link

Dapr initialized but Tye can't start on M1 with Colima and Minikube #1473

Closed GeofoxCoding closed 1 year ago

GeofoxCoding commented 1 year ago

Describe the bug

Hi, I'm new to Dapr and Tye and I would like to get a simple setup running locally with two .Net applications fontend/backend. I'm using a M1 Mac with Colima and minikube installed.

To Reproduce

colima start

minikube start

docker --version Docker version 20.10.21, build baeda1f82a

dapr init -k

dapr status -k NAME NAMESPACE HEALTHY STATUS REPLICAS VERSION AGE CREATED
dapr-operator dapr-system True Running 1 1.9.4 12m 2022-11-30 17:05.40
dapr-placement-server dapr-system True Running 1 1.9.4 12m 2022-11-30 17:05.40
dapr-sentry dapr-system True Running 1 1.9.4 12m 2022-11-30 17:05.40
dapr-sidecar-injector dapr-system True Running 1 1.9.4 12m 2022-11-30 17:05.40
dapr-dashboard dapr-system True Running 1 0.11.0 12m 2022-11-30 17:05.40 

      I'm starting dapper with -k because just 
      dapr init

      gives me:       
      ⌛  Making the jump to hyperspace...
     ❌  could not connect to Docker. Docker may not be installed or running

tye run Loading Application Details... Drats! 'run' failed: Dapr has not been initialized (e.g. via dapr init).

Dapr seems to be initialized correctly. Why can't Tye start?

Further technical details

tye --version 0.11.0-alpha.22111.1+3edef5428949c518c078844d6438e5ba86fce600

tye run -v debug Loading Application Details... Restoring and evaluating projects Resolved metadata for service dapr-api at .../Code/Dapr_Microservices/DAPR/API/DAPR.API/obj/Debug/net6.0/MicrosoftTye.ProjectMetadata.txt Resolved metadata for service dapr-blazor at .../Code/Dapr_Microservices/DAPR/Blazor/DAPR.Blazor/obj/Debug/net6.0/MicrosoftTye.ProjectMetadata.txt Restore and project evaluation took: 1873,4099ms Found application version: 1.0.0 RunCommand=.../Code/Dapr_Microservices/DAPR/API/DAPR.API/bin/Debug/net6.0/DAPR.API RunArguments= TargetPath=.../Code/Dapr_Microservices/DAPR/API/DAPR.API/bin/Debug/net6.0/DAPR.API.dll PublishDir=bin/Debug/net6.0/publish/ AssemblyName=DAPR.API IntermediateOutputPath=obj/Debug/net6.0/ Found target framework: net6.0 Parsed target framework name: net Parsed target framework version: 6.0 Found shared frameworks: Microsoft.NETCore.App, Microsoft.AspNetCore.App IsAspNet=True Evaluation Took: 1,0104ms Found application version: 1.0.0 RunCommand=.../Code/Dapr_Microservices/DAPR/Blazor/DAPR.Blazor/bin/Debug/net6.0/DAPR.Blazor RunArguments= TargetPath=.../Code/Dapr_Microservices/DAPR/Blazor/DAPR.Blazor/bin/Debug/net6.0/DAPR.Blazor.dll PublishDir=bin/Debug/net6.0/publish/ AssemblyName=DAPR.Blazor IntermediateOutputPath=obj/Debug/net6.0/ Found target framework: net6.0 Parsed target framework name: net Parsed target framework version: 6.0 Found shared frameworks: Microsoft.NETCore.App, Microsoft.AspNetCore.App IsAspNet=True Evaluation Took: 0,3184ms Drats! 'run' failed: Dapr has not been initialized (e.g. via dapr init).

GeofoxCoding commented 1 year ago

Sry, my mistake. I understand now that tye is not meant to be run against kubernetes which is for deploy.

I found out that I was missing a permanent entry for DOCKER_HOME pointing to my Colima docker.sock.

After that I was able to init dapr with docker setup und run tye.

Please keep on with this amazing project