GitXplorerGitXplorer
m

ros-docker

public
5 stars
2 forks
0 issues

Commits

List of commits on branch master.
Unverified
3ce18c8d77317c16ab42428924b36eaf8cffb31e

Update README with deprecation notice

mmvollrath committed 8 years ago
Unverified
77a66b311eb8affbf68e8fc724e24230c7a4bab2

Merge pull request #1 from minshallj/ft/spacenav_in_docker

mmvollrath committed 8 years ago
Unverified
4e20bf694df2dfde948b7c3b000b990c7856df03

added spacenav to dockerfile

mminshallj committed 9 years ago
Unverified
adfea69597fb50a79b91c1f1e847c5f5fe354c55

ROS docker build farm actually isn't done yet

mmvollrath committed 10 years ago
Unverified
d9f6c40e6c023e14560adfb6398b1c140794de09

Mention the official ROS build farm project

mmvollrath committed 10 years ago
Unverified
3b507a4ac310ee3bd929041dfe3f58757d000499

Initial commit

mmvollrath committed 10 years ago

README

The README file for this repository.

DEPRECATED

This repository is old, but might still have some hints if you're trying to use USB in Docker containers.

If you want to run ROS in Docker, see the ROS Docker wiki.

For accelerated graphics, see Hardware Acceleration in Docker

ros-docker

A Docker project for building, testing, installing, and running ROS software in a container with an exposed rosbridge node.

Why would you want to put ROS in a container?

ROS for OS X is unsupported, so this exists as a prepared solution for running tests, playing with rosbridge, developing roslibjs applications, or creating a container-ized build farm.

If you need an industrial strength build farm, refer to the ROS build farm project which is also based on Docker.

Building the image

Optionally, drop your ROS packages into src/. Any packages in this path will be built and installed. rosdep will attempt to install any declared dependencies.

By default, the container will run rosbridge websocket and rosapi nodes. Add any additional launch activity you want to user.launch.

If you're running your own packages, be sure to set up install targets in CMakeLists.txt or roslaunch won't be able to find your stuff.

Finally, build the container:

$ docker build -t rosdev /path/to/ros-docker

Running the image

Be sure to specify local port forwarding when starting the container.

Running in the foreground (with screen output from roslaunch):

$ docker run -p 9090:9090 -i -t --privileged -v /dev/bus/usb:/dev/bus/usb rosdev

Running in the background:

$ docker run -p 9090:9090 --privileged -v /dev/bus/usb:/dev/bus/usb -d rosdev

While the container is runnning, you should be able to connect to its rosbridge socket at ws://localhost:9090.

Verify in a Chrome dev console or use wscat:

$ wscat --connect ws://localhost:9090
connected (press CTRL+C to quit)
>

OS X

If you're using a Mac, you'll need to set up boot2docker.

Boot2Docker port forwarding

Once boot2docker is running and the docker command is working, run the boot2docker_forward.sh script to forward the rosbridge port through the VM.

Spacenav and LeapMotion

Make sure that spacenav isn't running on your host machine ps aux | grep spacenavd, and stop it if it is sudo service spacenavd stop Also make sure that there are no other rosdev docker images running spacenavd in the background either, docker ps will show you any running containers.