sysbox-ee icon indicating copy to clipboard operation
sysbox-ee copied to clipboard

ubuntu 19.04 server: runtime not found

Open streamnsight opened this issue 4 years ago • 3 comments

FYI:

I installed on Ubuntu 19.04 server from the live CD on VirtualBox. The installer gives an option to install Docker during installation of Ubuntu

Docker ends up under /var/snap/docker/384/run and the config is under /var/snap/docker/384/config

I am guessing this is why the daemon.json config file wasn't properly updated to include the runtime.

after updating the daemon.json config file with the path to the sysbox-runc runtime, the issue was resolved.

streamnsight avatar Sep 14 '19 19:09 streamnsight

@streamnsight thanks a bunch for looking into this.

Indeed, looks like we have an issue here as our installer is not taking into account Ubuntu's snap installation approach. Will fix this one asap.

rodnymolina avatar Sep 14 '19 19:09 rodnymolina

Issue workaround'ed by submitter, but a real fix is required from our side. Removing 'fixed' tag from this issue.

rodnymolina avatar Sep 21 '19 21:09 rodnymolina

Sysbox requires Docker be installed natively (not with the snap package). The Sysbox docs have been updated to make this clear. See here: https://github.com/nestybox/sysbox-external/blob/master/docs/user-guide/install.md

As mentioned above, when using the Docker snap, the docker daemon's config.json moves from /etc/docker/daemon.json -> /var/snap/docker/current/config/daemon.json.

But just updating this file to add info about the sysbox runtime is not sufficient. For some reason, the Docker installed via the snap can't see the sysbox-runc binary within it's chroot jail. Need to investigate this further.

ctalledo avatar Jul 08 '20 13:07 ctalledo