Problem running sysbox template with coder.

I discovered this template(https://github.com/sharkymark/v2-templates/tree/main/docker-in-docker), when tried make docker work in docker. Installed sysbox but on build state in coder i got error:
Error: Unable to start container: Error response from daemon: failed to create shim task: OCI runtime create failed: container_linux.go:425: starting container process caused: process_linux.go:607: container init caused: process_linux.go:578: handleReqOp caused: rootfs_init_linux.go:366: failed to mkdirall /var/lib/sysbox/shiftfs/8271c545-d14d-423d-891a-8bdba0e6f21e/var/lib/kubelet: mkdir /var/lib/sysbox/shiftfs/8271c545-d14d-423d-891a-8bdba0e6f21e/var/lib/kubelet: value too large for defined data type caused: mkdir /var/lib/sysbox/shiftfs/8271c545-d14d-423d-891a-8bdba0e6f21e/var/lib/kubelet: value too large for defined data type: unknown.
Error: Unable to start container: Error response from daemon: failed to create shim task: OCI runtime create failed: container_linux.go:425: starting container process caused: process_linux.go:607: container init caused: process_linux.go:578: handleReqOp caused: rootfs_init_linux.go:366: failed to mkdirall /var/lib/sysbox/shiftfs/8271c545-d14d-423d-891a-8bdba0e6f21e/var/lib/kubelet: mkdir /var/lib/sysbox/shiftfs/8271c545-d14d-423d-891a-8bdba0e6f21e/var/lib/kubelet: value too large for defined data type caused: mkdir /var/lib/sysbox/shiftfs/8271c545-d14d-423d-891a-8bdba0e6f21e/var/lib/kubelet: value too large for defined data type: unknown.
I dont have any idea whats wrong because other templates works fine.
23 Replies
Phorcys
Phorcys2y ago
can you send me your template (if you've done modifications to it) this is a system error though
BoJIwEbNuK
BoJIwEbNuKOP2y ago
Nothing changed. I just git cloned it. Seems like docker error and it's mean something with lvm partition I will try write in sysbox slack help message because it's because of sysbox. As workaround at sysbox slack channel they said try set flag --disable-shiftfs in sysbox systemd file. Or update to newer kernel, like 5.18+. I updated and now it builds I will finish my tests and then close this thread.
BoJIwEbNuK
BoJIwEbNuKOP2y ago
GitHub
Unable to start container with sysbox runtime after kernel update. ...
Running Ubuntu 22.04, and just received kernel update from 5.15.0-47 to 5.15.0-48, matching this security advisory, and It seems that containers can no-longer be started with the runtime:- https://...
BoJIwEbNuK
BoJIwEbNuKOP2y ago
oh, i got unable to connect
No description
BoJIwEbNuK
BoJIwEbNuKOP2y ago
something wrong, i always get unable to connect yes, something broken now. All my workspaces unable to connect Any ideas what's wrong?
Phorcys
Phorcys2y ago
i don't know sorry, never worked with sysbox, maybe this means the coder agent can't connect but i've never seen it look like that whoops, meant to ping @sharkymark lol thats a funny looking thing
sharkymark
sharkymark2y ago
sysbox is finicky. Nestybox (the company) was acquired by Docker earlier this year. So I am not aware of their support plans. https://www.nestybox.com/ I have another template that just creates a side-car with docker. I'd recommend this. https://github.com/sharkymark/v2-templates/tree/main/docker-in-docker/docker-with-side-car All of these are documented. https://coder.com/docs/coder-oss/latest/templates/docker-in-docker Good luck
Nestybox
Containers beyond Microservices
Use containers as virtual servers capable of running Docker, Kubernetes, and even legacy apps, seamlessly and securely.
GitHub
v2-templates/docker-in-docker/docker-with-side-car at main · sharky...
Contribute to sharkymark/v2-templates development by creating an account on GitHub.
Docker in Docker - Coder v2 main docs
Use docker inside containerized templates
BoJIwEbNuK
BoJIwEbNuKOP2y ago
Okay, will try. Thank you for your answer
Phorcys
Phorcys2y ago
well, he is using your template i think
BoJIwEbNuK
BoJIwEbNuKOP2y ago
Yes, hes template in v2 git that called docker-in-docker just like unable to connect And now all broken after sysbox, like unable to connect. To every workspace
Norbert Waszkowiak
I had the same problem today, I used only this (https://github.com/nestybox/sysbox/issues/596#issuecomment-1297185361) and it works for me
GitHub
Unable to start container with sysbox runtime after kernel update. ...
Running Ubuntu 22.04, and just received kernel update from 5.15.0-47 to 5.15.0-48, matching this security advisory, and It seems that containers can no-longer be started with the runtime:- https://...
BoJIwEbNuK
BoJIwEbNuKOP2y ago
I fixed problem with shiftfs just upgrading kernel, but now all my containers not work. I will try another example from sharkymark. And if it not work i dont know, will try method disabling shiftfs
sharkymark
sharkymark2y ago
the template implies a perfectly configured sysbox which sounded like the problem. works for me just fine.
BoJIwEbNuK
BoJIwEbNuKOP2y ago
You dont have error above on build state? What kernel you running?
sharkymark
sharkymark2y ago
I tried it again now -
No description
sharkymark
sharkymark2y ago
I can try the docker one
BoJIwEbNuK
BoJIwEbNuKOP2y ago
hm give me 1 minute i will try disabling shiftfs in sysbox
sharkymark
sharkymark2y ago
No description
BoJIwEbNuK
BoJIwEbNuKOP2y ago
Okay, i will try something Anyway thanks for your help
sharkymark
sharkymark2y ago
sure good luck
BoJIwEbNuK
BoJIwEbNuKOP2y ago
disabled shiftfs in sysbox, used your sysbox example, now all works. Thanks for your help
Phorcys
Phorcys2y ago
you can close the thread using /resolve
Codercord
Codercord2y ago
Marked the thread as resolved.
Want results from more Discord servers?
Add your server