- 03 Jan, 2022 1 commit
-
-
Ben Cooksley authored
This is a temporary fix.
-
- 02 Jan, 2022 3 commits
-
-
Ben Cooksley authored
-
-
Ben Cooksley authored
Another Python module we need, not sure why Linux has this installed by default yet Windows does not...
-
- 01 Jan, 2022 17 commits
-
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
Split the Windows images in two - a base image for use by Craft and a more complete one for CI use on Gitlab
-
Ben Cooksley authored
-
- 31 Dec, 2021 12 commits
-
-
Ben Cooksley authored
-
Ben Cooksley authored
Lets try this again - this time with the process isolation flag instead
-
Ben Cooksley authored
Turns out Docker for Windows is a massive snowflake when it comes to the --memory option, which for us is a bit of a worry when it comes to some of our builds... Lets try just 2GB
-
Ben Cooksley authored
Microsoft documentation indicates that the VS installation process can also require more memory than the 1GB usually allowed during Docker image builds. Increase the limit accordingly (they suggest 2GB, but for extra safety lets make it 4GB)
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
-
Ben Cooksley authored
Long story short - you cannot use installers that potentially have a GUI component within a Windows container unless you run them under cmd /S /C. See https://jfreeman.dev/blog/2019/07/09/what-i-learned-making-a-docker-container-for-building-c++-on-windows/ for more details. Switch from Powershell to Cmd.exe for MS Build Tools runs
-
Ben Cooksley authored
-
Ben Cooksley authored
-
- 12 Dec, 2021 2 commits
-
-
Ben Cooksley authored
-
Ben Cooksley authored
-