In order for Golem to work it needs to create a Docker VM, this allows for computations to be completed in an isolated environement from the Requestor and Provider host machines. Below you will see a list of common Docker Errors from Golem.log files, along with some troubleshooting tips.
If you cannot find your golem.log file, check here for instructions on log locations.
ERROR golem.docker.manager b"VirtualBox: error creating VM 'golem': Command '['docker-machine', 'create', '--driver', 'virtualbox', 'golem']' returned non-zero exit status 3."
WARNING golem.docker.manager b'DockerMachine: failed to env the VM: Command '['docker-machine', 'env', '--shell', 'cmd', 'golem']'
If you see either of these two errors in your golem.log file, then follow these troubleshooting steps:
Shutdown the Golem App
Open Docker Quickstart Terminal (You can find it in your programs or as an icon on your desktop)
This command shows if docker is running any errors. It is good to run this command before and after running any of the following docker commands to see if the error is solved.
docker-machine restart golem
This will restart docker’s golem instance.
docker-machine rm golem
This will remove the docker container.
Outside of the Docker Quickstart Terminal you can remove .docker C:\Users\%USER%.docker\machine\machines\golem
You can search for this directory in your Windows search bar and remove it. This will force remove the docker machine from the docker directory. Then run the following command in Docker Quickstart Terminal:
docker-machine create golem --driver virtualbox
This will create and engage the necessary drivers for your docker machine
_WARNING golem.docker.taskthread Task stderr:/usr/bin/python: can't open file '/golem/work/job.py': [Errno 2] No such file or directory
If you receive this error in your golem.log file, then the directory for the docker and data drive is not using the same hard drive as your Golem app. You just need to move your docker directory to the same hard drive as your Golem directory.