posit/connect-content-init repository overview

⁠

⁠Posit Connect Content Init container image

This container image is an init container for Connect that pulls runtime components into a shared volume. The Connect Launcher then uses those components to build and run published content in separate pods. This image is for Off-Host Execution (OHE) deployments on Kubernetes and is the default init container in the Connect Helm chart.

⁠Quick reference

⁠Related images

For Kubernetes deployments, Connect uses three images together. See the repository README⁠ for Helm configuration.

⁠How to use this image

⁠With the Connect Helm chart

The Connect Helm chart⁠ uses this image as the default for OHE deployments in chart versions >= 0.20.0. See the image migration guide⁠ for upgrading from earlier versions.

⁠As a Kubernetes init container

To wire the image up directly in a pod spec, mount a shared volume at /mnt/rstudio-connect-runtime. The entrypoint copies the runtime components from /opt/rstudio-connect-runtime in the image into that path. The Connect content container then mounts the same volume to consume the runtime.

initContainers:
  - name: connect-content-init
    image: ghcr.io/posit-dev/connect-content-init:2026.09.0
    volumeMounts:
      - name: connect-runtime
        mountPath: /mnt/rstudio-connect-runtime
volumes:
  - name: connect-runtime
    emptyDir: {}

⁠Image tags

Posit publishes images to:

• Docker Hub: docker.io/posit/connect-content-init
• GitHub Container Registry: ghcr.io/posit-dev/connect-content-init

Ubuntu 24.04 is the default OS.

Tag formats where YYYY.MM.P is any supported Connect version:

• YYYY.MM.P - Default OS
• YYYY.MM.P-ubuntu-24.04 - Explicit OS
• YYYY.MM.P-ubuntu-22.04 - Older OS
• latest - Latest version, default OS

⁠Architectures

Posit publishes multi-arch images for both linux/amd64 and linux/arm64. Pull the same tag from either platform. Docker selects the matching manifest automatically.

⁠Volumes

The init container copies runtime components from /opt/rstudio-connect-runtime in the image into /mnt/rstudio-connect-runtime on the shared volume.

The content execution container mounts the same volume to consume the runtime files at the path Connect expects.

⁠User

The container starts as root so the entrypoint can write files into the shared volume with the permissions Connect expects. The init container exits after the copy completes. If your cluster requires non-root init containers, you can override the user, but ensure the override has write access to the shared volume mount path.

⁠Examples

⁠Extending with custom content

You can extend this image to include additional content beyond the default set. For example, you can add custom R packages, Python packages, or system dependencies that your published content requires. See Custom Container Images for Connect⁠.

For a full guide to which Connect image to customize for different goals, see the Connect extending examples⁠.

⁠Migrating from legacy image

This image replaces the legacy rstudio/rstudio-connect-content-init⁠ image. The init container behavior is unchanged. The entrypoint copies runtime components into a shared volume at /mnt/rstudio-connect-runtime for the Connect content container to consume. The differences lie in how the image is published.

⁠Image references

Posit published the legacy image as rstudio/rstudio-connect-content-init on Docker Hub and ghcr.io/rstudio/rstudio-connect-content-init on GHCR, tagged by OS (jammy, ubuntu2204, jammy-<version>, ubuntu2204-<version>) for linux/amd64 only. Update your image reference to one of the new locations and pick a tag that pins to your desired Connect version and OS. See Image tags⁠ and Architectures⁠.

⁠Base OS options

The legacy image shipped Ubuntu 22.04 only. This image adds Ubuntu 24.04 as the default OS while still publishing Ubuntu 22.04 tags. See Image tags⁠.

⁠What did not change

• Source path for runtime components (/opt/rstudio-connect-runtime)
• Target path on the shared volume (/mnt/rstudio-connect-runtime)
• Entrypoint behavior (one-shot copy, then exit)
• Compatibility with the Connect Helm chart and Connect Launcher

⁠Caveats

⁠Security

Review these images before using them in production. Organizations with specific Common Vulnerabilities and Exposures (CVE) or vulnerability requirements should rebuild these images to meet their security standards.

Posit rebuilds published images weekly for Posit product editions under active support, pulling in operating system patches.