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 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.
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:
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
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
The text was updated successfully, but these errors were encountered: