no-volume initialize containers fails

Hi,

We are testing the kubernetes-novolume mode on the arc, and when used with this job, the initialize container fails

Controler and scaleset charts: version 0.13.0
ghcr.io/actions/actions-runner:2.330.0

##[debug]Evaluating condition for step: 'Initialize containers'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Initialize containers
##[debug]Register post job cleanup for stopping/deleting containers.
Run '/home/runner/k8s-novolume/index.js'
##[debug]/home/runner/externals/node20/bin/node /home/runner/k8s-novolume/index.js
##[debug]Job pod created, waiting for it to come online <EDITED>
##[debug]Copying /home/runner/_work to pod <EDITED> at /__w
(node:5521) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Error: Executing the custom container implementation failed. Please contact your self hosted runner administrator.
##[debug]System.Exception: Executing the custom container implementation failed. Please contact your self hosted runner administrator.
##[debug] ---> System.Exception: Response file could not be read at '/home/runner/k8s-novolume/index.js' running command 'PrepareJob'
##[debug]   at GitHub.Runner.Worker.Container.ContainerHooks.ContainerHookManager.GetResponse[T](HookInput input)
##[debug]   at GitHub.Runner.Worker.Container.ContainerHooks.ContainerHookManager.ExecuteHookScript[T](IExecutionContext context, HookInput input, ActionRunStage stage, String prependPath)
##[debug]   --- End of inner exception stack trace ---
##[debug]   at GitHub.Runner.Worker.Container.ContainerHooks.ContainerHookManager.ExecuteHookScript[T](IExecutionContext context, HookInput input, ActionRunStage stage, String prependPath)
##[debug]   at GitHub.Runner.Worker.Container.ContainerHooks.ContainerHookManager.PrepareJobAsync(IExecutionContext context, List`1 containers)
##[debug]   at GitHub.Runner.Worker.ContainerOperationProvider.StartContainersAsync(IExecutionContext executionContext, Object data)
##[debug]   at GitHub.Runner.Worker.JobExtensionRunner.RunAsync()
##[debug]   at GitHub.Runner.Worker.StepsRunner.RunStepAsync(IStep step, CancellationToken jobCancellationToken)
##[debug]Finishing: Initialize containers

Other workflows work with kubernetes-novolume, and this specific job worked fine with kubernetes mode

  setup_vars:
    name: Feature Branch Init
    container:
      image: alpine/k8s:1.28.0
    env:
      RELEASE_NAME: ${{ needs.setup_vars.outputs.branch_name }}
    steps:
      - uses: FranzDiebold/github-env-vars-action@v2
      # Conditional step to exit if on excluded branch
      - name: Check branch
        run: |
          if [ "${{ github.ref }}" == "refs/heads/main" ]; then
            echo "This workflow cannot run on 'main'. Exiting."
            exit 1
          fi
      - name: Set branch_name
        id: setup-vars
        run: |
          # Take the first 15 characters and remove trailing dashes
          branch_name=$(echo "${CI_ACTION_REF_NAME_SLUG:0:15}" | sed 's/-*$//')
          echo "branch_name=$branch_name" >> $GITHUB_OUTPUT
    outputs:
      branch_name: ${{ steps.setup-vars.outputs.branch_name }}

Start with the kubernetes-novolume hook entry point at /home/runner/k8s-novolume/index.js and trace the PrepareJob response handling shown in the log. Compare this path with the working kubernetes mode and reproduce the setup_vars job using the listed chart and runner versions; done means the Initialize containers step completes without the response-file error.