You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last two arguments must be provided, since the default path for the environment is set to /home/otc/ObstacleTower/obstacletower.x86_64 which does not exist.
Please add --rm tag when launching docker containers:
Do docker run --rm (other parameters...) all the time, otherwise lots of exited docker containers are going to be left behind, which consume disk space.
By the way, somehow the docker that runs ./run.sh doesn't terminate after the evaluation is done, we need to manually kill it by doing ctrl+c. Here's the output after ctrl+c:
^CTraceback (most recent call last):
File "run.py", line 35, in <module>
env.close()
File "/srv/conda/lib/python3.6/site-packages/obstacle_tower_env.py", line 231, in close
time.sleep(10)
KeyboardInterrupt
It looks like that it is stucked at closing the environment. I'm guessing it is trying to close an environment that is already closed (by the docker running env.sh)?
The text was updated successfully, but these errors were encountered:
Hi @kwea123 We've just updated env.sh as follows: 33becd9. This should alleviate some of your issues. We will look into the second problem of ensuring the process ends correctly.
I ran into some problems when launching docker, here are some of my suggestions:
The last two arguments must be provided, since the default path for the environment is set to
/home/otc/ObstacleTower/obstacletower.x86_64
which does not exist.--rm
tag when launching docker containers:Do
docker run --rm (other parameters...)
all the time, otherwise lots of exited docker containers are going to be left behind, which consume disk space.By the way, somehow the docker that runs
./run.sh
doesn't terminate after the evaluation is done, we need to manually kill it by doing ctrl+c. Here's the output after ctrl+c:It looks like that it is stucked at closing the environment. I'm guessing it is trying to close an environment that is already closed (by the docker running
env.sh
)?The text was updated successfully, but these errors were encountered: