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

Radius + Dapr Tutorial Does not Work #1895

Open
harivamsi9 opened this issue Dec 7, 2024 · 1 comment
Open

Radius + Dapr Tutorial Does not Work #1895

harivamsi9 opened this issue Dec 7, 2024 · 1 comment
Labels
bug Something is broken or not working as expected triaged This item has been triaged by project maintainers and is in the backlog

Comments

@harivamsi9
Copy link

harivamsi9 commented Dec 7, 2024

Bug information

Steps to reproduce (required)

Followed the "Dapr Microservices" Tutorial https://docs.radapp.io/tutorials/dapr/

I was using the recommended k3d for the local kuberneters

created a cluster using
k3d cluster create -p "8081:80@loadbalancer" --k3s-arg "--disable=traefik@server:*" --k3s-arg "--disable=servicelb@server:*"

rad install kubernetes --set rp.publicEndpointOverride=localhost:8081

rad init
dapr init -k

then
rad run dapr.bicep

Observed behavior (required)

Frontend container is failing.

dump of output logs:

rad run dapr.bicep                                                                                                                                                 ─╯
Building dapr.bicep...
WARNING: The following experimental Bicep features have been enabled: Extensibility. Experimental features should be enabled for testing purposes only, as there are no guarantees about the quality or stability of these features. Do not enable these settings for any production usage, or your production environment may be subject to breaking.
Deploying template 'dapr.bicep' for application 'dapr' and environment '/planes/radius/local/resourceGroups/default/providers/Applications.Core/environments/default' from workspace 'default'...

Deployment In Progress... 

Completed            statestore1     Applications.Dapr/stateStores
Completed            dapr1           Applications.Core/applications
Completed            backend1        Applications.Core/containers
...                  frontend        Applications.Core/containers
Error: {
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please see the details for the specific operation that failed.",
  "target": "/planes/radius/local/resourceGroups/default/providers/Microsoft.Resources/deployments/rad-deploy-d294c1ef-2f61-4c67-8f18-1587e99e0e34",
  "details": [
    {
      "code": "",
      "message": ""
    },
    {
      "code": "ResourceDeploymentFailure",
      "message": "Failed",
      "target": "/planes/radius/local/resourceGroups/default/providers/Applications.Core/containers/frontend",
      "details": [
        {
          "code": "Internal",
          "message": "Container state is 'Waiting' Reason: CrashLoopBackOff, Message: back-off 10s restarting failed container=frontend pod=frontend-6d97848cd5-985cp_default-dapr1(38ce54f7-a2de-4ea6-8672-5771fafc3608) LastTerminationState: "
        }
      ]
    },
    {
      "code": "",
      "message": ""
    },
    {
      "code": "OK",
      "message": "",
      "target": "/planes/radius/local/resourceGroups/default/providers/Applications.Dapr/stateStores/statestore1"
    },
    {
      "code": "OK",
      "message": "",
      "target": "/planes/radius/local/resourceGroups/default/providers/Applications.Core/containers/backend1"
    },
    {
      "code": "OK",
      "message": "",
      "target": "/planes/radius/local/resourceGroups/default/providers/Applications.Core/applications/dapr1"
    }
  ]
}

TraceId:  f5ab188b9f82ab7315a0d59a11e92153

Desired behavior (required)

Fronend Container is launches properly, and the deployment is executed and it should provide me a way to check and confirm that deployment.

Workaround (optional)

System information

Mac Pro M3

rad Version (required)

RELEASE VERSION BICEP COMMIT
0.40.0 v0.40.0 0.31.92 91603b305b56c8245b3d3250bb6253c7ab436aae

Operating system (required)

macOS 15.1.1 (24B91), M3 chip

Additional context

The other containers were launched successfully. but not the frontend one.
I did some debugging, and I believe the frontend container was compiled on a different architecture.
I am using Mac Pro M3, so I guess that is why the frontend container is just failing to even launch.

AB#13784

@harivamsi9 harivamsi9 added the bug Something is broken or not working as expected label Dec 7, 2024
@lakshmimsft lakshmimsft added the triaged This item has been triaged by project maintainers and is in the backlog label Dec 9, 2024
@willtsai
Copy link
Contributor

I can confirm the same behavior on my M1 Mac setup:

kubectl get pods -n default-dapr 
NAME                       READY   STATUS             RESTARTS           AGE
backend-85d6d57b44-9qwjg   2/2     Running            6 (27h ago)        20d
frontend-887994548-fsh2b   1/2     CrashLoopBackOff   3715 (4m44s ago)   20d
> rad version
RELEASE   VERSION   BICEP     COMMIT
0.39.0    v0.39.0   0.31.34   c83b37888b959cff0d2bebaecec5643bd908b308

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken or not working as expected triaged This item has been triaged by project maintainers and is in the backlog
Projects
None yet
Development

No branches or pull requests

3 participants