Closed bytepoet closed 2 months ago
Thanks for raising this issue. My first suspicion is that Docker isn't installed in the standard location, because of this log excerpt:
/usr/bin/runc: No such file or directory
It's likely that RunCVM currently requires Docker to be installed in a standard location/installed from Docker's packages. We might be able to address this, once we understand the issue.
Please elaborate on your system environment, ie Linux distribution name and version, and how you have Docker installed (e.g. using Docker's packages, the distribution's packages, Snap, or other).
Also please provide the output of which runc
.
Same issue, I installed docker using apt install docker.io
The solution is to do this ln -s /usr/sbin/runc /usr/bin/runc
Would be great if the installation script could auto detect this :)
@jimaek That's excellent news. In your case it looks like you're using the Ubuntu or Debian distribution packages rather than the Docker packages RunCVM has been developed against.
I'll raise an issue to find a way to address this (preferably without having to tamper with the filesystem by creating a symlink but by finding the installed runc path and using that).
In the meantime it's great to have a workaround.
@bytepoet Are you using the docker.io package too?
@jimaek Your issue is now here: https://github.com/newsnowlabs/runcvm/issues/20
I'll keep the current issue open for now in case it turns out the specifics of @bytepoet's case are different.
Thank you!
@jimaek this was exactly the issue! thanks for this.
@struanb I appreciate the attention you've given, thanks for making this project.
The below is on a fresh VM in the cloud. I would expect it to pull the docker container and drop me into a shell with the openwrt runtime but i get the following:
Any help is appreciated.