eriba
eriba4mo ago

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.
8 Replies
Leokuma
Leokuma4mo ago
Are you able to provide a simplified, reproducible code snippet?
eriba
eribaOP4mo ago
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.
Leokuma
Leokuma4mo ago
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, IDK
eriba
eribaOP3mo ago
same 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.
Testersen™
Testersen™3mo ago
We're running Deno in Azure through AKS. Works perfectly fine.
again
again3mo ago
@eriba you should open a GitHub issue and provide as much information as possible.
creoman
creoman3w ago
We are experiencing the same issue with Deno in Azuer Container Apps, starting from 2.1.5 We found that the issue is reproducible when container apps has Virtual Network attached (no outbound rules). It runs fine in a container environment without a virtual network. Also tried adding OTEL_DENO=false, this didn't help.
Vadem
Vadem2w ago
Just to mention: I've created an issue regarding this problem because it affects current deno version v2.2.11 https://github.com/denoland/deno/issues/29036
GitHub
Deno exits with 1 exit code with no logs or error details in Azure ...
Version: from Deno 2.1.5 From discord help thread: https://discord.com/channels/684898665143206084/1327331978055385250 We are experiencing the same issue with Deno in Azuer Container Apps, starting...

Did you find this page helpful?