Skip to content

Explain why ca-certificates is required in the Node Dockerfile template#849

Open
aryeila wants to merge 3 commits into
mainfrom
chana/docs-1454-ca-certificates-comment
Open

Explain why ca-certificates is required in the Node Dockerfile template#849
aryeila wants to merge 3 commits into
mainfrom
chana/docs-1454-ca-certificates-comment

Conversation

@aryeila
Copy link
Copy Markdown

@aryeila aryeila commented May 27, 2026

Rewrite the in-template ca-certificates comment in pkg/agentfs/examples/node.Dockerfile to explain why the line is load-bearing.

node:22-slim doesn't ship the system CA bundle, so Node agents on it fail with a misleading failed to retrieve region info error. The previous comment ("enables TLS/SSL for securely fetching dependencies") implied this was generic Docker hygiene that could be trimmed, and users were doing exactly that. Reproduced and verified end-to-end against a live LiveKit Cloud project.

No functional change. Filed against DOCS-1454.

Related PRs

Same change applied across the docs partial and sibling repos so they stay aligned:

The previous comment ("enables TLS/SSL for securely fetching dependencies")
implied this is generic Docker hygiene that could be skipped to shave layers.
That framing is misleading: @livekit/rtc-node ships a native Rust core that
reads the system trust store via rustls-tls-native-roots, not Node's bundled
CA roots. node:22-slim doesn't ship /etc/ssl/certs/ca-certificates.crt, so
without ca-certificates Room.connect() fails with the misleading
"failed to retrieve region info" error.

Rewrite the in-template comment to name the cause so a developer trimming the
image knows the line is load-bearing. No functional change.
@aryeila aryeila marked this pull request as ready for review May 28, 2026 22:08
@aryeila aryeila requested review from bcherry, kath0la and royalfig May 28, 2026 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant