Design 'Otterly Confused by This Error' on Sticker at Spreadshirt » easily removable, weatherproof, durable ✓ easy returns ✓ Discover Stickers now!

A cute and funny programmer-inspired design featuring an adorable confused otter staring at a laptop error message. Perfect for developers, coders, programmers, software engineers, tech workers, and a...

Hi HF team, Since this morning, paid GPU Spaces fail to start on every GPU pool I can try (L4, A10G) with the same OCI runtime error at container-init time. I’ve confirmed the identical failure live on several unrelated public Spaces across T4 / L4 / A10G. ZeroGPU Spaces seem unaffected. **Error (verbatim from the runtime errorMessage):** ``` 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?) ``` **Reproduced today (UTC) on public Spaces — all still RUNTIME_ERROR:** Space | Hardware | Notes ---|---|--- ggml-org/gguf-my-repo | a10g-large | same error AlicanKiraz0/Trendyol-TTS-Space | t4-small | same error HuggingFaceM4/faster-qwen3-tts-demo | a10g-small | same error (Docker SDK) vLAR/GPU-Test | l4x1 | failed with this exact error at 07:52:59 UTC today; owner seems to have switched it to cpu-basic since **My Spaces** (private; were starting and running fine earlier today with unchanged code): * l4x1: failed identically * a10g-large: failed identically * happy to share full build/container logs on request **Troubleshooting already done:** 1. Minimal repro: a Gradio Space whose entire app.py is `import gradio as gr`, `import spaces` and a trivial `@spaces.GPU` function — fails at the same container-init step, before any application code executes. So this is not application code. 2. Build completes fully (all pip installs succeed). The failure is strictly at runc container creation (mount of `/usr/bin/nvidia-cuda-mps-control`). 3. Both Gradio SDK (sdk_version 5.50.0 and 6.26.0) and Docker SDK Spaces are affected. 4. status.huggingface.co shows Spaces “Operational” and no incident is listed. **Questions:** 1. Is there a known incident affecting idmap mounts / user namespaces on paid GPU nodes? 2. If not — is there anything we can change on our side? The failure happens before any app code runs, and the only real lever left (hardware flavor) reproduces the error on both pools I’ve tried. ZeroGPU works, but its quotas don’t fit GPU-heavy workloads. Thanks a lot!

Hi HF team, Since this morning, paid GPU Spaces fail to start on every GPU pool I can try (L4, A10G) with the same OCI runtime error at container-init time. I’ve confirmed the identical failure live on several unrelated public Spaces across T4 / L4 / A10G. ZeroGPU Spaces seem unaffected. **Error (verbatim from the runtime errorMessage):** ``` 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?) ``` **Reproduced today (UTC) on public Spaces — all still RUNTIME_ERROR:** Space | Hardware | Notes ---|---|--- ggml-org/gguf-my-repo | a10g-large | same error AlicanKiraz0/Trendyol-TTS-Space | t4-small | same error HuggingFaceM4/faster-qwen3-tts-demo | a10g-small | same error (Docker SDK) vLAR/GPU-Test | l4x1 | failed with this exact error at 07:52:59 UTC today; owner seems to have switched it to cpu-basic since **My Spaces** (private; were starting and running fine earlier today with unchanged code): * l4x1: failed identically * a10g-large: failed identically * happy to share full build/container logs on request **Troubleshooting already done:** 1. Minimal repro: a Gradio Space whose entire app.py is `import gradio as gr`, `import spaces` and a trivial `@spaces.GPU` function — fails at the same container-init step, before any application code executes. So this is not application code. 2. Build completes fully (all pip installs succeed). The failure is strictly at runc container creation (mount of `/usr/bin/nvidia-cuda-mps-control`). 3. Both Gradio SDK (sdk_version 5.50.0 and 6.26.0) and Docker SDK Spaces are affected. 4. status.huggingface.co shows Spaces “Operational” and no incident is listed. **Questions:** 1. Is there a known incident affecting idmap mounts / user namespaces on paid GPU nodes? 2. If not — is there anything we can change on our side? The failure happens before any app code runs, and the only real lever left (hardware flavor) reproduces the error on both pools I’ve tried. ZeroGPU works, but its quotas don’t fit GPU-heavy workloads. Thanks a lot!