SIVACOR only allows you to run certain well-defined software stacks, packaged as Docker images, from known and trusted sources. The table below shows all available software images with their tags and links to their Docker Hub repositories. If you believe additional images should be added, file a pull request at the sivacor-repo-choice repository, and contact us.
Stata images are built by the AEA Data Editor, with permission from StataCorp. See the dataeditors repositories for more information. Stata containers define Stata versions, with tags identifying the within-version regular updates. Usually, you can use the latest tag for a specific version. Images contain no user-installed packages (net install, ssc install, etc.). You must provide an installation script that adds any such packages into a project-specific folder, see Step 0.
We use a subset of images from the rocker project for R. See the rocker repositories for more information. An image name is defined by a combination of pre-installed packages. Any additional packages must be installed, using an appropriate method, see Step 0. Tags identify different versions of R.
We use images from dynare/dynare for MATLAB, because they contain most MATLAB toolboxes. Only certain versions of MATLAB are supported. You should use these even if you do not use Dynare. Tags identify a particular combination of Dynare and MATLAB versions.
Julia containers differ only minimally from official Julia images. They add a non-root user, and make efficiency simplifications for the package registry, see SIVACOR/julia. Images are available at ghcr.io/sivacor.
Containers are named after the Julia release — julia1.10, julia1.11 — and a tag per build,
<julia version>-<build date>. New tags are created either when a new Julia release is made, or when the underlying Linux container is updated. Pick the version matching the Julia you developed against, and the newest tag
within it.
Julia containers do not include any packages. Use Project.toml to add packages; see Step 0.