Docker images for local WebKit development and CI/CD on Windows.

Using the webkitdev Docker images requires a Windows host, ideally Windows 11 or Windows Server 2022 but Windows 10 and Windows Server 2019 can also be used, with Docker installed and targeting Windows containers. For new installs follow the latest documentation to setup Windows for containers.

The webkitdev Docker images include the required software to build WebKit on Windows. Docker images can descend from each other, following a single inheritance model like in Object-Oriented Programming (OOP). The images in the table below are organized by purpose and include all components of the previous image. In practice users will likely only ever need the msbuild-2022 one for local builds or buildbot-worker for running CI/CD within the WebKit infrastructure.

Docker images support tagging. For Windows images the tag references the version of the container base image, Windows Server 2022 and Windows Server 2019. Compatibility depends on what the host OS is. In general Windows 11 needs to target 2022 tags and Windows 10 needs to target 2019 tags. For the latest information on Windows container version compatibility see the documentation.

The windows-<version> have a larger base image containing more Windows OS components making them ideal for testing WebKit. The other tags use Windows Server Core and are suitable for building WebKit.

Run the Build-All.ps1 PowerShell script to build the images. It expects a single argument -Tag which specifies the tag to build. Use the ☝️ table to determine what value to use.

After the script completes run docker images and verify the images are present and tagged. The created time should be within the time frame the script was executing in.

With the webkitdev/msbuild-2022 image everything is there to do a build of the Windows WebKit port. Start out by doing a local checkout of the WebKit repository. The docker run command needs to be populated with the following fields.

docker run --name build --rm -it `
    --cpu-count=<cpu-count> --memory=<memory> `
    --volume <volume>:C:/webkit `
    webkitdev/msbuild-2022:<tag> powershell

As an example a Windows 11 host having 8 logical cores and 32GB of memory containing a checkout of WebKit at C:\GitHub\webkit would run the container like this 👇.

docker run --name build --rm -it `
    --cpu-count=6 --memory=16g `
    --volume C:/GitHub/webkit:C:/webkit `
    webkitdev/msbuild-2022:2022 powershell

Once the command is run it will place you into a Powershell session. From there execute the following to build the Windows WebKit port.

Select-VSEnvironment
$env:CC = "clang-cl.exe"
$env:CXX = "clang-cl.exe"
cd C:\webkit
perl Tools\Scripts\build-webkit

After completion the artifacts end up in the WebKitBuild directory within the checkout. The Buildbots for the Windows WebKit port use these Docker containers so they should build WebKit without issue. However if there any problems with the images feel free to open an issue.