Skip to content

Explain why ca-certificates is required in the Dockerfile#50

Draft
aryeila wants to merge 1 commit into
mainfrom
chana/docs-1454-ca-certificates-comment
Draft

Explain why ca-certificates is required in the Dockerfile#50
aryeila wants to merge 1 commit into
mainfrom
chana/docs-1454-ca-certificates-comment

Conversation

@aryeila
Copy link
Copy Markdown
Contributor

@aryeila aryeila commented May 27, 2026

Overview

Rewrite the in-Dockerfile ca-certificates comment to explain why the line is load-bearing. No functional change.

@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 installed, Room.connect() fails with the 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.

End-to-end Docker repro confirms the failure mode (slim Node without ca-certificates reproduces the exact error string from livekit/agents-js#932) and the fix.

Context

Filed against DOCS-1454.

Related PRs

The same comment rewrite is 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 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 comment to name the cause so a developer trimming the image
knows the line is load-bearing. No functional change.
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