concourse-sysbox

> Question: did you start sysbox-mgr and sysbox-fs? No I did not. I assumed (incorrectly) that sysbox-runc was all that was needed. I will attempt to run these and get...

I can confirm that sysbox-fs and sysbox-mgr are running (both in /usr/bin). I now get different errors than before: ``` run check: find or create container on worker worker1: starting...

@ctalledo Thank you for the help so far. I have more information. Rather than get this to work with concourse, I figure I would check to make sure everything is...

Update here that I am able to get sysbox-runc working with docker. Using docker:dind image confirms that docker-in-docker can run without "--privileged". However when I start concourse it directly talks...

The contents of `/etc/sub{u|g}id` looks the same and as follows: ``` user1:100000:65536 user2:165536:65536 user3:231072:65536 user4:296608:65536 user5:362144:65536 user6:427680:65536 sysbox:493216:65536 ``` I generally don't know anything about these files.

> is there a flag similar to Docker's --runtime flag, so you can tell it to use sysbox-runc? Not that I'm aware of. There is a way to pass a...

What I know right now is: - sysbox-runc works with docker, by modifying `/etc/docker/daemon.json` and also by passing `--runtime` - using containerd through concourse binary and directly replacing oci-runc with...

'm symlinking my otherwise oci spec compatible runc binary to point over to sysbox-runc, and that's when I'm getting the error. My understanding is that the host ID issue is...