[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"problem-detail-error-container-creating":3},{"stack":4,"error":5,"seoName":6,"seoStack":7,"seo":8,"breadcrumb":10,"titlePrefix":16,"titleAccent":17,"lead":18,"facts":21,"why":34,"log":44,"fix":77,"engine":93,"related":101,"pitch":115},"all","container-creating","Nested Docker startup failed","PanelAlpha Engine",{"description":9},"Learn what causes Nested Docker startup failed, how PanelAlpha Engine responds to it during deployment.",[11,14],{"label":12,"href":13},"App Installations","\u002Fapps",{"label":15},"Nested Docker startup failed: Sysbox runtime unavailable","Nested Docker startup failed: ","Sysbox runtime unavailable",[19],{"text":20},"Error recorded 6 times in PanelAlpha Engine deploys. The deploy log below is the recorded failure output.",[22,27,30],{"label":23,"value":24,"tone":25,"tooltip":26},"Type","Error","err","An 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.",{"label":28,"value":29},"Seen","6 times · 3 variants",{"label":31,"value":32,"tooltip":33},"Status","Observed (2.1.0)","Our team will look into this soon, verify the cause and try to fix it in an upcoming release.",{"heading":35,"body":36},"Why it happens",[37,39,42],{"text":38},"The deploy reached the preparing stage but could not start the DinD account container. Sysbox could not connect to its host service socket at ",{"text":40,"code":41},"\u002Frun\u002Fsysbox\u002Fsysfs.sock",true,{"text":43},", indicating that the Sysbox service is stopped, unhealthy, or inaccessible. The application build did not start.",{"heading":45,"block":46},"What the log looks like",{"header":47,"lines":48},"Deploy log",[49,53,57,61,65,69,73],{"segments":50},[51],{"text":52},"Starting stage: preparing",{"segments":54},[55],{"text":56},"service \"dind\" is not running",{"segments":58},[59],{"text":60},"Error response from daemon: failed to create task for container:",{"segments":62},[63],{"text":64},"failed to create shim task: OCI runtime create failed:",{"segments":66},[67],{"text":68},"failed to get config from sysbox-fs:",{"segments":70},[71],{"text":72},"rpc error: code = Unavailable desc = connection error:",{"segments":74},[75],{"text":76},"dial unix \u002Frun\u002Fsysbox\u002Fsysfs.sock: connect: connection refused",{"heading":78,"steps":79,"block":90},"How to fix it",[80],[81,83,84,86,88],{"text":82},"On the host, verify that the Sysbox service is running and that ",{"text":40,"code":41},{"text":85}," exists and is accessible. Restart or repair Sysbox, then confirm Docker can start a container using ",{"text":87,"code":41},"sysbox-runc",{"text":89},". Retry the deploy after the host runtime is healthy.",{"header":91,"lines":92},"Fix by hand",[],{"heading":94,"body":95,"block":98},"How PanelAlpha Engine solves it",[96],{"text":97},"Detect the Sysbox socket and service health before deployment, and report a host-runtime remediation instead of the generic preparing failure. The Engine should also avoid treating the DinD service as simply not running when container creation failed at the OCI runtime layer.",{"header":99,"lines":100},"",[],{"heading":102,"items":103},"Apps affected",[104,108,112],{"title":105,"badge":106,"tone":25,"href":107},"Chatwoot","4 occurrences","\u002Fapps\u002Fchatwoot\u002Fchatwoot",{"title":109,"badge":110,"tone":25,"href":111},"expense-tracker-app","1 occurrence","\u002Fapps\u002Fmanthanank\u002Fexpense-tracker-app",{"title":113,"badge":110,"tone":25,"href":114},"getkirby\u002Fstarterkit","\u002Fapps\u002Fgetkirby\u002Fstarterkit",{"heading":116,"body":117,"footNote":118,"docsLabel":119,"docsHref":120},"Try PanelAlpha Engine yourself.","The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.","Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPU","Read the documentation","https:\u002F\u002Fpanelalpha.com\u002Fdocs"]