Getting started
Three ways to use this project, depending on where you want the container to run.
Pick an entry point
GitHub Codespaces
Open a container in the browser or in your desktop editor, with nothing installed locally. Best for trying Quarto, running a workshop, or reproducing a bug report.
Dev Containers
Run the same container on your own machine with Docker and the Dev Containers extension or CLI. Best for day-to-day work on an existing project.
As a template
Copy the repository and keep only the configuration you need. Best when you want your own project to ship a Quarto container.
The quickest path
Launch a Codespace on this repository with either image.
Purpose-built image
Uses ghcr.io/mcanouil/quarto-codespaces:latest, described in container images. Everything is preinstalled, so it starts fastest.
Universal base image
Uses the universal configuration, built on Microsoft’s Codespaces base image. It consumes less of your GitHub storage quota.
Then what?
Once the container is up, quarto check reports the state of every engine. The Quarto check output page shows what the latest build produces, so you can compare against a known-good run.
Language environments are not created for you. Run init-env.sh when you want a project-local renv, uv, or Julia environment.