Requirements

Note

Hyper-V Windows featureis not really required if you use process isolation for both the image build & runtime.

How to

Important

If using Docker Desktop - first make sure you have switched toContainers for Windows. If you are CLI user and have client & daemon headless, then use appropriate windows build context.

Run container from github container registry

docker run-it-p80:10240 ghcr.io/devsh-graphics-programming/compiler-explorer-docker:nano-2022

or build image yourself

git clone https://github.com/Devsh-Graphics-Programming/Compiler-Explorer-Docker.git

docker build--isolation"process"-t godbolt/nano .

Tip

I highly recommend to build the image without virtualization (process isolation) to use all host resources, HyperV isolation will assign 1/2 CPUs + 1GB of RAM by default hence the result could be < 10x slower buildwithout assigning cpu resources by hand. If you get an error and can't use process isolation it's because your host kernel version is too low - update your OS or switch to HyperV (skip--process "isolation" flag).

Tip

The image is built with default set of options, there are a few you can override (eg. NodeJS version, remote & sha of CE). SeeDockerfile code for more details.

docker run-p80:10240-it godbolt/nano

Important

You should use produced image as base to provide your own compilers (installation binaries) & configuration files for CE to use them. By default we run it without any compilers.

Production example