Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancements of docker environment setup #24

Open
kwea123 opened this issue Mar 6, 2019 · 1 comment
Open

Enhancements of docker environment setup #24

kwea123 opened this issue Mar 6, 2019 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@kwea123
Copy link
Contributor

kwea123 commented Mar 6, 2019

I ran into some problems when launching docker, here are some of my suggestions:

  1. When launching the environment, the correct command should be the following:
docker run \
  --env OTC_EVALUATION_ENABLED=true \
  --env OTC_DEMO_EVALUATION=true \
  --network=host \
  -it obstacle_tower_challenge:latest ./env.sh 5005 ObstacleTower/obstacletower.x86_64

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.

  1. 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)?

@awjuliani
Copy link
Contributor

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.

@awjuliani awjuliani self-assigned this Mar 6, 2019
@awjuliani awjuliani added the bug Something isn't working label Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants