Nested Docker startup failed: Sysbox runtime unavailable
Error recorded 6 times in PanelAlpha Engine deploys. The deploy log below is the recorded failure output.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen6 times · 3 variants
StatusObserved (2.1.0)Our team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The deploy reached the preparing stage but could not start the DinD account container. Sysbox could not connect to its host service socket at /run/sysbox/sysfs.sock, indicating that the Sysbox service is stopped, unhealthy, or inaccessible. The application build did not start.
What the log looks like
Deploy log
Starting stage: preparingservice "dind" is not runningError response from daemon: failed to create task for container:failed to create shim task: OCI runtime create failed:failed to get config from sysbox-fs:rpc error: code = Unavailable desc = connection error:dial unix /run/sysbox/sysfs.sock: connect: connection refused