Skip to content

Node docker image cannot use TLS #1661

Description

@Mirko-von-Leipzig

This is because the image base excludes the TLS system libs which in turn does not allow the image to connect to https externally.

This is a problem for multiple reasons, including the inability to connect to provers or export telemetry which use https (which should be all/most).

We can either choose a less cut back base image, or figure out which libs are required as part of the base to enable TLS/CA support.

Activity

  1. added this to the v0.13.0 milestone on Feb 10, 2026
  2. modified the milestones: v0.13.0, v0.14.0 on Mar 18, 2026
  3. modified the milestones: v0.14.0, v0.15.0 on Apr 1, 2026
  4. namedfarouk commented on Apr 30, 2026

    @namedfarouk
    Contributor

    Hi maintainers, I’d like to work on this issue. Could you please assign it to @namedfarouk? I can open a focused PR with tests after assignment.

  5. Mirko-von-Leipzig commented on May 1, 2026

    @Mirko-von-Leipzig
    CollaboratorAuthor

    @namedfarouk I would be careful of overusing AI for this - it may need some more thought e.g. put into the base image for example.

  6. namedfarouk commented on May 1, 2026

    @namedfarouk
    Contributor

    I’ve opened a PR for this:

    The fix keeps the runtime image minimal but adds ca-certificates to the node Docker runtime base so outbound https connections work in containerized deployments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

nodeRelated to the node component

Type

Fields

Priority

None yet

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions