gesistsa
A collection of post-installation steps
- rmarkdown / latex:
RUN apt-get -y install pandoc pandoc-citeproc texlive - quarto:
RUN apt-get install -y curl git && curl -LO https://quarto.org/download/latest/quarto-linux-amd64.deb && dpkg -i quarto-linux-amd64.deb && quarto install tool tinytex && rm quarto-linux-amd64.deb - clean:
RUN rm -rf /var/lib/apt/lists/* && if [ -d "$CACHE_PATH" ]; then rm -rf $CACHE_PATH; fi - make:
RUN apt-get -y install make
ttps://quarto.org/download/latest/quarto-linux-amd64.deb redirects to the last stable version (https://github.com/quarto-dev/quarto-cli/releases/download/v1.2.475/quarto-1.2.475-linux-amd64.deb at the time of writing). My experience is that quarto is still very new and development is fast. Because of this, I'm always using the pre-release (https://github.com/quarto-dev/quarto-cli/releases) and, in my Dockerfile, I have
curl -L $(curl https://quarto.org/docs/download/_prerelease.json | grep -oP "(?<=\"download_url\":\s\")https.*amd64\.deb") -o /tmp/quarto.deb
@chainsawriot perhaps there should be one text file generation function that can simply insert "RUN", "ENV" and other keywords if it is generating a Dockerfile and %post/%environment, etc. sections if it is generating Appatiner/Singularity definition.
So maybe I should not have renamed COPY to FILES and RUN to POST in the apptainerize() function.
