setting up ID-mapped mount on path l/MC5NLBMOUWRCMT7APIL35VNLEZ (likely means idmapped mounts are not supported on the filesystem at this path ()) caused: Failed to eval symlink on : lstat l: no such file or directory: unknown.

Linux ccts192 6.1.0-26-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux

Docker version 27.3.1.

Installed sysbox-ce_0.6.6-0.linux_amd64.deb.

gcr.io/cloudshell-images/cloudshell:latest is gcr.io/cloudshell-images/cloudshell@sha256:160f8d278d62b745f187d5916aac199482e4c04af11a26f268cd7885f4e3ce47

docker run -it --rm --entrypoint bash gcr.io/cloudshell-images/cloudshell:latest succeeds and I can get to shell prompt.

docker run -it --rm --runtime sysbox-runc --entrypoint bash gcr.io/cloudshell-images/cloudshell:latest fails with:

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: container_linux.go:439: starting container process caused: process_linux.go:608: container init caused: process_linux.go:579: handleReqOp caused: rootfs_init_linux.go:317: setting up ID-mapped mount on path l/MC5NLBMOUWRCMT7APIL35VNLEZ (likely means idmapped mounts are not supported on the filesystem at this path ()) caused: Failed to eval symlink on : lstat l: no such file or directory: unknown.

cc @wy0464

Start by reproducing the two Docker commands with sysbox-runc on the reported Debian 6.1.112-1 cloud kernel, using the specified Cloud Shell image. Compare the successful default runtime with the failing sysbox-runc startup and investigate the reported ID-mapped mount and symlink path; done means identifying a reproducible cause and a confirmed resolution or limitation.