-
Notifications
You must be signed in to change notification settings - Fork 75
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
Unable to launch robot server within docker container. #81
Comments
Hi @szhaovas, have you tried replacing |
Hi @jr-b-reiterer, Thank you for the reply. Yes, I replaced |
When I test with your image, the behaviour is different: I get past the lines from your screenshot, but then the reset fails. The warning from gym I get there gave me a hint that you are using a too new version of gym, 0.26. robo-gym in the present version is compatible with gym up to 0.21 only because of their API change. (An upgrade of robo-gym is in the works internally.) Back to your observation: I am using Docker 20.10.21 on Ubuntu 20.04. I am not sure if any difference here could cause the problem. You could test if it is different when you run your test script not in a tmux pane but in a separate terminal that you connect to your running container in addition: |
Hi @jr-b-reiterer, I downgraded gym to 0.21, and I am now getting the same error as you. I tried both running |
I am not sure it will fix your issue, but apparently your downgrade of gym was not successful. The passive env checker that outputs the warning in your screenshot does not exist in Gym v0.21, see |
Update: got it to work with 2 fixes!
|
Hello developers, thank you for maintaining robo-gym!
I have been having troubles running robo-gym inside a docker container. My goal is to run the robo-gym server side from within the container, and run the robo-gym training script on my host machine. However, I cannot seem to launch robot server inside the container, and the application always stalls on the step
Starting Robot Server...
.I initially thought it to be a docker port problem, but even if I launched both the server and the training script within the same docker container, I still could not launch the server, as shown (
test.py
in the right pane is simply the Random Agent MiR100 Simulation Environment example in README):Steps to reproduce
docker pull szhaovas/robogym_test
.noetic.Dockerfile
at my fork of the robo-gym-robot-servers repo. This dockerfile is similar to your original, except it also installs robo-gym for running the training script.docker run --rm -it szhaovas/robogym_test
.start-server-manager && attach-to-server-manager
.python3 test.py
.My setup
Additional info
self.tmux_srv.new_session
line inside ServerManager.new_session().kill-all-robot-servers
, it returns the error messageerror connecting to /tmp/tmux-0/ServerManager (No such file or directory)
.Thanks in advance!
The text was updated successfully, but these errors were encountered: