initial commit for updated docker process.

[AustinDeric]

Work in Progress. This is the initial peak at the docker solution to #96. The next commit will be the example images. I setup automatic builds on dockerhub at:
https://hub.docker.com/r/austinderic/gym-gazebo/

I recommend the same thing for erlerobitcs when we get this merged in. If you add me to the admins then i can help out with that.

[vmayoral]

Thanks for this @AustinDeric!

[AustinDeric]

UPDATE: I am not considering this a WIP anymore.

i have everything working and running out of a docker container. However, the simulation isn't running. In order to reproduce:

docker run -it --rm \
  -p "80:8080" \
  --name=gym-gazebo-turtlebot \
  austinderic/gym-gazebo-turtlebot:kinetic \
  /bin/bash

Then, in the container, run the following command to start gzweb and the gym-gazebo turtlebot example:

npm run start --prefix ./gzweb/ & \
 python /root/gym-gazebo/examples/turtlebot/circuit2_turtlebot_lidar_qlearn.py

Lastly, open your browser and navigate to localhost

It appears that the gym-gazebo/examples/turtlebot/circuit2_turtlebot_lidar_qlearn.py script does not progress past the observation = env.reset() line:

gym-gazebo/examples/turtlebot/circuit2_turtlebot_lidar_qlearn.py

Line 48 in 0001678

observation = env.reset()

[AustinDeric]

I spent a little bit of time on this issue. It seems the point cloud is not generated. After so research i found this gem:
https://github.com/turtlebot/turtlebot_simulator/blob/c5806a922d6b3d60d6e82a22a12da94978940c23/turtlebot_gazebo/launch/includes/kobuki.launch.xml#L21

<!-- Bumper/cliff to pointcloud (not working, as it needs sensors/core messages) -->
<include file="$(find turtlebot_bringup)/launch/includes/kobuki/bumper2pc.launch.xml"/>

[pulver22]

@AustinDeric I have the same problem, basically turtlebot doesn't move at all. Did you solve this issue?

[AustinDeric]

@AustinDeric I have the same problem, basically turtlebot doesn't move at all. Did you solve this issue?

no :(

[pulver22]

@AustinDeric actually I was able to make it work uninstalling the project and reinstalling everything (dependencies included) using python2 and pip2.7 . I may think it's due to a communication error between Py3 and Ros Kinetic (py2-based).