Open Garwakizashi opened 6 months ago
@Garwakizashi There is no known issue with Dapr integration with ACA. We have variety of Apps running in ACA and could not see any reason why it won't work for you. Can you please raise a support ticket with more details about your App Env and other details to debug this better? Please link this GitHub issue to be aware of the context.
@Garwakizashi There is no known issue with Dapr integration with ACA. We have variety of Apps running in ACA and could not see any reason why it won't work for you. Can you please raise a support ticket with more details about your App Env and other details to debug this better? Please link this GitHub issue to be aware of the context.
Thanks for the reply. I wasn't able to figure why it wouldn't work, but I managed to get around it by running the nextjs app behind nginx. Once it was behind nginx, the dapr sidecar started successfully.
+1
Also facing this issue with ACA. Locally I can run de Nextjs app with Dapr without issues. When deploying to ACA, Dapr gives the same error has stated by @Garwakizashi
This issue is a: (mark with an x)
Issue description
Not sure if this can be classed as a bug, as it is very likely I'm missing on my end to get this working; but I'd like to get some guidance with this issue I'm having.
I'm trying to enable dapr on an ACA that runs a nextjs application.
The application itself is running on port
3000
, and that is also what I've set the app-port of dapr to be as well. However, the the container just keeps crashing, looking at the logs of daprd, it just shows the debug message several times:before eventually:
I did notice that it said it is waiting on the port, but the application never gets discovered. Could this be why it is failing? Is there a requirement on my side to set up in nextjs to allow dapr to discover it? The ACA ingress port is also set to
3000
, and is working as expected. I have several ACA's that are working fine with dapr enabled, so not sure why this particular app would fail. Unsure if this helps, but I've been able to run dapr locally and the application gets discovered fine.Steps to reproduce
Expected behavior Daprd container to work. Actual behavior Daprd container keeps restarting due to the described error above.
Additional context
Sample logs from log stream (removed instance name):