Please reference the list below for public Civis docker images and their associated packages:
|
Image |
Description/Notes |
Supported Versions |
| civis-jupyter-python3 |
The image used for Python Notebooks. |
2, 3, 4
Deprecated and unsupported after 2021-02-01: 1.9, 1.10, 1.11, 1.12 |
| civis-jupyter-r |
The image used for R Notebooks. |
2, 3 Deprecated and unsupported after 2024-12-31: 1.11.0 |
| civis-services-flask |
An image for deploying Flask apps in Platform. |
latest |
| civis-services-shiny |
An image for deploying R Shiny apps in Platform |
>=1.4 |
| civis-services-streamlit |
An image for deploying Python Streamlit apps in Platform |
1 |
| datascience-python |
The image used for Python3 Scripts. This can also be used for Container Scripts. |
6, 7
Deprecated and unsupported after 2021-02-01: 2.0 through 5.0 |
| datascience-r |
The image used for R Scripts. This can also be used for Container Scripts. |
5, 6 Deprecated and unsupported after 2024-12-31: 2.8, 3, 4 |
The Docker images have versions that follow semantic versioning (e.g., “6.2.1”), and three tags are created or updated when a new version is released: a tag with the major version (e.g., “6”), a tag with the minor version (e.g., “6.2”), and a tag with the patch version (e.g., “6.2.1”). Pinning Scripts or Notebooks to a major version should suffice to avoid breaking changes that would require you to change your code, but you may wish to pin to the more specific minor or patch versions for reproducibility. Note that the more specific versions are less likely to receive security patches and bug fixes.
Comments
0 comments
Please sign in to leave a comment.