rstudio/content-base repository overview

⁠content/base

This is a basic image with:

• "most" system dependencies for basic examples
• A single R version
• A single Python version

You must build the content-base image before you can build the content-pro image

⁠content/pro

This is a basic image with RStudio Pro drivers installed. These images are built using the content-base images as the base docker image. Thus, the content-base image with the corresponding R and Python version must have been built prior to building these pro images. Attempting to build a pro image using a content-base image that does not exist will result in an error.

⁠Examine images

The scripts/build-image-yaml.sh script that runs the scripts/examine-image.sh analysis script within a container. It emits progress information to stderr and the resulting YAML to stdout.

This command produces the YAML for a single image.

./scripts/build-image-yaml.sh rstudio/content-base:r3.6.3-py3.8.8-bionic > runtime.yaml

This command generates a single YAML for the available rstudio/content-base images:

./scripts/build-image-yaml.sh rstudio/content-base:r3.1.3-py2.7.18-bionic \
		rstudio/content-base:r3.2.5-py2.7.18-bionic \
		rstudio/content-base:r3.3.3-py3.6.13-bionic \
		rstudio/content-base:r3.4.4-py3.6.13-bionic \
		rstudio/content-base:r3.4.4-py3.7.10-bionic \
		rstudio/content-base:r3.5.3-py2.7.18-bionic \
		rstudio/content-base:r3.5.3-py3.7.10-bionic \
		rstudio/content-base:r3.6.3-py2.7.18-bionic \
		rstudio/content-base:r3.6.3-py3.6.13-bionic \
		rstudio/content-base:r3.6.3-py3.8.8-bionic  \
		rstudio/content-base:r4.0.5-py3.6.13-bionic \
		rstudio/content-base:r4.0.5-py3.7.10-bionic \
		rstudio/content-base:r4.0.5-py3.8.8-bionic  \
		rstudio/content-base:r4.0.5-py3.9.2-bionic  \
		rstudio/content-base:r4.1.0-py3.8.8-bionic  \
		rstudio/content-base:r4.1.0-py3.9.2-bionic  > runtime.yaml

This command generates a single YAML for the available rstudio/content-pro images:

./scripts/build-image-yaml.sh rstudio/content-pro:r3.1.3-py2.7.18-bionic \
		rstudio/content-pro:r3.2.5-py2.7.18-bionic \
		rstudio/content-pro:r3.3.3-py3.6.13-bionic \
		rstudio/content-pro:r3.4.4-py3.6.13-bionic \
		rstudio/content-pro:r3.4.4-py3.7.10-bionic \
		rstudio/content-pro:r3.5.3-py2.7.18-bionic \
		rstudio/content-pro:r3.5.3-py3.7.10-bionic \
		rstudio/content-pro:r3.6.3-py2.7.18-bionic \
		rstudio/content-pro:r3.6.3-py3.6.13-bionic \
		rstudio/content-pro:r3.6.3-py3.8.8-bionic  \
		rstudio/content-pro:r4.0.5-py3.6.13-bionic \
		rstudio/content-pro:r4.0.5-py3.7.10-bionic \
		rstudio/content-pro:r4.0.5-py3.8.8-bionic  \
		rstudio/content-pro:r4.0.5-py3.9.2-bionic  \
		rstudio/content-pro:r4.1.0-py3.8.8-bionic  \
		rstudio/content-pro:r4.1.0-py3.9.2-bionic  > runtime.yaml

The NO_PATH_LOOKUPS environment variable indicates that PATH is ignored when attempting to discover R, Python, and Quarto installations.

NO_PATH_LOOKUPS=1 ./scripts/build-image.sh \
    rstudio/content-pro:r3.1.3-py2.7.18-bionic > runtime.yaml

The DEBUG environment variable produces additional output about the image analysis.

DEBUG=1 ./scripts/build-image.sh \
    rstudio/content-pro:r3.1.3-py2.7.18-bionic > runtime.yaml

⁠Build matrix

The CONTENT_BUILD_MATRIX variable defined in the buildx bake definition⁠ is used to determine which combinations of R and Python to use when building our content-base and content-pro images. To add a new R and Python version combination, simply update the matrix and the Github Action will publish the new image combinations to our registries upon the next push to main.

To build content images locally, use just bake content-images from the repository root.

⁠Github Actions

Content base and pro images are built in build-bake⁠.

⁠Licensing

The license associated with the RStudio Docker Products repository is located in LICENSE.md⁠.

As is the case with all container images, the images themselves also contain other software which may be under other licenses (i.e. bash, linux, system libraries, etc., along with any other direct or indirect dependencies of the primary software being contained).

It is an image user's responsibility to ensure that use of this image (and any of its dependent layers) complies with all relevant licenses for the software contained in the image.