Deno exits with 1 exit code with no logs or error details in Azure Container App

[ardasovvadim]

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 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.

Additional details:

• Affected version from 2.1.5 till the new release 2.2.11
• We tried examples from official documentation with simple "Hello Word" server: https://docs.deno.com/runtime/reference/docker/
• Container will not spin app at all. Connecting to the container and running the cmd "deno --version" will respond correctly. Any other cmds like "deno", "deno run", "deno cache", "deno test" exist with 1 exit code and no logs.
• Precompiled version via "deno compile" has the same issue.

Container with deno 2.1.5

# deno --version
deno 2.1.5 (stable, release, x86_64-unknown-linux-gnu)
v8 13.0.245.12-rusty
typescript 5.6.2
# deno
# deno test
# deno main.ts

Container with deno 2.1.4

# deno --version
deno 2.1.4 (stable, release, x86_64-unknown-linux-gnu)
v8 13.0.245.12-rusty
typescript 5.6.2
# deno
Deno 2.1.4
exit using ctrl+d, ctrl+c, or close()
REPL is running with all permissions allowed.
To specify permissions, run `deno repl` with allow flags.
> 
press ctrl+c again to exit
> 
# deno test
Check file:///app/main_test.ts
running 1 test from ./main_test.ts
addTest ... ok (0ms)

ok | 1 passed | 0 failed (3ms)

# deno main.ts
Add 2 + 3 = 5
# 

[dsherret]

Maybe try running with --log-level=debug to see if it gives any more information?

[ardasovvadim]

Maybe try running with --log-level=debug to see if it gives any more information?

Deno doesn't respond except deno --version command.

Container with deno 2.2.10

# deno --version
deno 2.2.10 (stable, release, x86_64-unknown-linux-gnu)
v8 13.5.212.10-rusty
typescript 5.7.3
# deno --log-level=debug
# deno test --log-level=debug
# deno run main.ts --log-level=debug

I am just looking into list of changes of 2.1.5 and wondering can it be somehow related to:

1. fix(ext/net): update moka cache to avoid potential panic in Deno.resolveDns
   on some laptops with Ryzen CPU (fix(ext/net): update moka cache to avoid potential panic in Deno.resolveDns on some laptops with Ryzen CPU #27572)
2. feat(unstable): implement QUIC (feat(unstable): Implement QUIC #21942)

I guess azure adds some default restrictions on network level or user group and can cause the problem.

If you need Azure CLI script to set up the environment with the official deno container, let me know.

[dsherret]

FWIW, it's possible to test each commit by doing deno upgrade <commit-hash-on-main>. That might help identify which commit caused this before we have a chance to take a look. No idea what's causing this.

[dsherret]

This might be fixed by #29065 (deno upgrade 229228ae0d7c58e1d78dc1777e5f43afe4a58d33)

[tomas-zijdemans-vipps]

deno upgrade 229228ae0d7c58e1d78dc1777e5f43afe4a58d33 solved this exact issue for my apps.

(Ps. Please note that I am deploying on Azure Kubernetes Service, no Azure Container Apps)

[dsherret]

Looks like the reason it didn't output anything was due to #28796

I'm going to close this one as fixed because it should output the error in the next release or in canary.