I'm now getting this error in several sandboxes, which seems to only be fixed by sbx rm to remove the sandbox (which loses data):
ERROR: failed to start sandbox: sandboxd error: status 500: failed to start runtime: Error response from daemon: creating containerd task for container 6d711cfc2573: failed to create shim task: mount source: "overlay", target: "/run/bundles/6d711cfc257378ca3fb117a9f5ac2a7e1a3d6e04d441bb7be2ce26ff014becdf/rootfs", fstype: overlay, flags: 0, data: "workdir=/run/bundles/6d711cfc257378ca3fb117a9f5ac2a7e1a3d6e04d441bb7be2ce26ff014becdf/mounts/0/work,upperdir=/run/bundles/6d711cfc257378ca3fb117a9f5ac2a7e1a3d6e04d441bb7be2ce26ff014becdf/mounts/0/upper,lowerdir=/run/bundles/6d711cfc257378ca3fb117a9f5ac2a7e1a3d6e04d441bb7be2ce26ff014becdf/mounts/1", err: stale file handle
I've seen sbx run claude -- --print get stuck and kill it when that happens, so these sandboxes have probably been force quit several times.
I'm now getting this error in several sandboxes, which seems to only be fixed by
sbx rmto remove the sandbox (which loses data):I've seen
sbx run claude -- --printget stuck and kill it when that happens, so these sandboxes have probably been force quit several times.