All paid GPU pools fail to start: MOUNT_ATTR_IDMAP error at container init (Exit code 128)

Every paid GPU pool on Hugging Face Jobs and Spaces has failed to start since about 00:10 UTC on 2026-09-25, aborting 4 seconds after launch with exit code 128 and the error "failed to set MOUNT_ATTR_IDMAP on /usr/bin/nvidia-cuda-mps-control: invalid argument," according to a user report. The affected flavors are t4-small, l4x1 and a10g-small, while cpu-basic still runs; the last successful GPU job completed at 20:34 UTC on 2026-09-24. The failures reproduce on stock public images including nvidia/cuda:12.4.1-base-ubuntu22.04, pytorch/pytorch:2.6.0-cuda12.4-cudnn9-devel and python:3.12-slim, even when running only a GPU check, and Hugging Face's status page still lists Jobs as operational.

Same error on Hugging Face Jobs, not only Spaces, and it started earlier than the first reports here. Since about 00:10 UTC on 2026-09-25, every GPU job on my account fails 4 s after it starts with exit code 128: failed to set MOUNT ATTR IDMAP on /usr/bin/nvidia-cuda-mps-control: invalid argument Flavours affected: t4-small, l4x1, a10g-small. cpu-basic still runs. The last GPU job that succeeded was at 20:34 UTC on 2026-09-24. It fails on stock public images running nothing but a GPU check: nvidia/cuda:12.4.1-base-ubuntu22.04 nvidia-smi 07:47 and ~08:10 UTC pytorch/pytorch:2.6.0-cuda12.4-cudnn9-devel torch.cuda check ~07:51 UTC python:3.12-slim nvidia-smi 07:45 UTC The status page still shows Jobs as operational. Job IDs are available to HF staff on request.