deno 2.1.5 not running in Azure Container App environment
I was using
FROM denoland/deno:latest in my Dockerfile and after the deno 2.1.5 release new replicas want deploy to CA environments, the container starts but immediately terminates.
Tried pulling the deployed image locally and it runs on my Windows PC on docker desktop without any issues.
I fixed the image to FROM denoland/deno:2.1.4 which solves the issue on Azure CA environment but think there might be some underlying compatibility issues.6 Replies
Are you able to provide a simplified, reproducible code snippet?
that would be rather difficult an time consuming. I'd need to provision a new container environment and CA, setup a ci/cd pipeline and worst of all, since it runs locally it would be trial and error with a full deployment cycle in between.
No worries. I was just wondering if the "problem" was in the Deno runtime itself or in your code. Wondering if the app was just one line - a simple
console.log, or a Deno.serve() - it would work or not. The guys are implementing Otel, maybe it has something to do with the problem, IDKsame issue with 2.1.6, container starts and immediately terminates, had to revert to 2.1.4 again
same issue with 2.1.7. This is getting annoying :hooray_deno:
any chance this gets fixed? We have Deno 2.2.1 already and this is still not fixed.
We're running Deno in Azure through AKS. Works perfectly fine.
@eriba you should open a GitHub issue and provide as much information as possible.