Exit code: 128. Reason: failed to create containerd task:

Spaces
1

Hi HF team,

Our Space whisperx-transcription is consistently failing to start with the same container-runtime error, across three separate attempts today (two Factory Rebuilds and one normal rebuild triggered by a commit):

Exit code: 128. Reason: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: failed to fulfil mount request: failed to set MOUNT_ATTR_IDMAP on /usr/bin/nvidia-cuda-mps-control: invalid argument (maybe the filesystem used doesn’t support idmap mounts on this kernel?)

This fails at container init, before our application code runs, so it doesn’t appear to be anything in our Dockerfile or app. We’ve already ruled out our own code as the cause:

  • Build phase always completes successfully.
  • The failure happens identically at container start every time.
  • We’ve tried: Factory Rebuild (twice) and a fresh commit-triggered rebuild — all three attempts hit the exact same error

I have no idea what could be the problem and how to fix it

1 Like