Skip to content

Commit bf5eb6a

Browse files
[CI] Perform runs in a container volume
This patch makes the windows builds run in a volume rather than the container's scratch space. This is necessary given we cannot increase the default scratch space maximum from its default of 20GB through kubernetes.
1 parent ad9a7f6 commit bf5eb6a

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

premerge/windows_runner_values.yaml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,3 +31,16 @@ template:
3131
env:
3232
- name: DISABLE_RUNNER_UPDATE
3333
value: "true"
34+
# Add a volume/mount it to C:/_work so that we can use more than 20GB
35+
# of space. Windows containers default to only having 20GB of scratch
36+
# space and there is no way to configure this through kubernetes
37+
# although the underlying containerd runtime should support it. So
38+
# instead we just use a emptyDir volume mounted at C:/_work, which is
39+
# where the GHA runner does everything.
40+
volumeMounts:
41+
- name: builddir
42+
mountPath: "C:/_work"
43+
volumes:
44+
- name: builddir
45+
emptyDir: {}
46+

0 commit comments

Comments
 (0)