-
Notifications
You must be signed in to change notification settings - Fork 17
Building a new Docker image manually
Only change the Dockerfile
and install_packages.R
files in csasdown
if it is to be a global feature addition for all users.
For personal changes only you will make a new, personal image which you then run. It won't be part of the csasdown
image. Copy/paste the docker
directory into another directory on your machine called myproj/docker
for this wiki where you can edit them.
Open the Linux shell (or Powershell) and navigate to the myproj/docker
directory and made your changes to the Dockerfile
and/or install_packages.R
file, build the image. but first pull rocker/tidyverse
to get the newest version of everything inside R that this project is based on:
docker pull rocker/tidyverse
Then build the image:
docker build . --no-cache -t mydocker_username/myproj
If you are satisfied with your new image you can push it to your Docker Hub account if you want. This assumes you made an account with the user name mydocker_username
. Docker knows the URL and will push directly to DockerHub.
docker push mydocker_username/myproj
If you find that when using the docker image cgrandin/csasdown you always have some manual steps after like adding new LaTeX packages and installing new R packages, you may want to add those things to the docker image locally so that you don't have to repeat them each time you open the RStudio instance. To do that, edit the Dockerfile
for additional LaTeX packages and the install_packages.R
file for additional R packages. If the changes are worthy of passing along to other users we can add them directly to the cgrandin/csasdown
image.