Using helper image gitlab-runner-helper:x86_64-v16.11.1-nanoserver21H2 results in init-permissions error
## Summary When using nanoserver helper image `gitlab-runner-helper:x86_64-v16.11.1-nanoserver21H2` job fails with error: ``` Warning Failed Error: failed to start containerd task "init-permissions": hcs::System::CreateProcess init-permissions: The system cannot find the file specified.: unknown ``` ## Steps to reproduce 1. In runner configuration, use helper image: ``` helper_image = "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v17.1.0-nanoserver21H2" ``` 2. Run a job. It fails: ``` Warning Failed Error: failed to start containerd task "init-permissions": hcs::System::CreateProcess init-permissions: The system cannot find the file specified.: unknown WARNING: Event retrieved from the cluster: Error: failed to start containerd task "init-permissions": hcs::System::CreateProcess init-permissions: The system cannot find the file specified.: unknown ERROR: Job failed (system failure): prepare environment: waiting for pod running: pod status is failed. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information ``` <!-- Please add the definition of the job from `.gitlab-ci.yml` that is failing inside of the code blocks (```) below. --> <details> <summary> .gitlab-ci.yml </summary> ```yml Add the job definition that is failing here ``` </details> ## Actual behavior nanoserver helper image causes failure when starting init-permissions. ## Expected behavior nanoserver helper image should work without errors. ## Relevant logs and/or screenshots <!-- Paste the job logs inside of the code blocks (```) below so it would be easier to read. --> <details> <summary> job log </summary> ```sh Running with gitlab-runner 16.11.1 (535ced5f) on gitlab-runner-b5474989-htt6k _Q6ecjTkG, system ID: r_sSOkTCq4QMeh feature flags: FF_USE_POWERSHELL_PATH_RESOLVER:true, FF_SCRIPT_SECTIONS:true, FF_RETRIEVE_POD_WARNING_EVENTS:true, FF_PRINT_POD_EVENTS:true Preparing the "kubernetes" executor 00:00 Using Kubernetes namespace: default Using Kubernetes executor with image mcr.microsoft.com/windows/servercore:ltsc2022 ... Using attach strategy to execute scripts... Preparing environment 00:18 Using FF_USE_POD_ACTIVE_DEADLINE_SECONDS, the Pod activeDeadlineSeconds will be set to the job timeout: 30m0s... Subscribing to Kubernetes Pod events... Type Reason Message Normal Scheduled Successfully assigned default/runner-q6ecjtkg-project-25452826-concurrent-0-5fhfx99w to gke-ab2d29-hx1o Normal Pulling Pulling image "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v17.1.0-nanoserver21H2" Normal Pulled Successfully pulled image "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v17.1.0-nanoserver21H2" in 6.672s (6.672s including waiting) Normal Created Created container init-permissions Warning Failed Error: failed to start containerd task "init-permissions": hcs::System::CreateProcess init-permissions: The system cannot find the file specified.: unknown WARNING: Event retrieved from the cluster: Error: failed to start containerd task "init-permissions": hcs::System::CreateProcess init-permissions: The system cannot find the file specified.: unknown ERROR: Job failed (system failure): prepare environment: waiting for pod running: pod status is failed. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information ``` </details> cc. @ratchade
issue