Closed themoddedcube closed 3 years ago
Try docker ps
to see if the sagemaker is running in the background. Sometimes, it starts very slow on some machines. Just wait a bit and If you see sagemaker on the running docker list, then enter dr-logs-sagemaker
to see logs. If not, maybe something wrong in your reward function, hyperparameters, action space, or even env settings.
When I re-installed and ./init again, the same error occurred.(in my case, ./init error)
In my case, I initialized docker swarm and ran . /init. After initializing the docker swarm and running ./init, sagemaker started.
so my suggestioin is
docker swarm leave -f
docker swarm init
./init
@porygon-git I always ignore these errors. ./init.sh
tries to initialize and join the swarm. Since you've initialized before, it cannot be joined again.
Closing as question resolved.
I followed the video tutorial on this, and I keep getting the error that sagemaker is not running. I have pulled the correct image and have checked the system.env file to make sure I got the right image. Can anyone please help me with this?