Skip to content

dfvneto/docker_ros

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

37 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


Logo

Docker script to build ROS docker image
Report Bug · Request Feature

Table of Contents

About The Project

This is a docker image to use ROS without it destroying your developing environment :D

Built With/Using

  • Docker
  • Shell Script

Getting Started

To get a local copy up and running follow these simple steps.

Prerequisites

You need to install Docker. For a more detailed explanation about Docker and Containers see: https://www.docker.com/get-started

  • Docker installation
sudo apt-get -y install curl apt-transport-https ca-certificates software-properties-common

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

sudo apt-get update

sudo apt-get install docker-compose docker docker-ce
  • Use docker without sudo (optional)
sudo groupadd docker

sudo usermod -aG docker $USER

su - ${USER}

id -nG

Installation

  1. Clone the docker_ros
git clone https:://github.com/dfvneto/docker_ros.git
  1. Build Docker Image
./build.sh

Usage

After installation, your docker image should have been built correctly. Now we have to access it:

  1. Accessing Docker Container
./access_docker.sh
  1. Now we can run our roscore node inside the container
roscore

Note that our terminal is "locked", so we need to access our container through another terminal.

  1. Open another terminal on the root folder and run:
docker ps

Look for the container ID of our recently created image ros_melodic:$USER.

  1. Using the container ID run:
./new_view.sh DOCKER_ID

When inside the docker, you'll notice that the ros commands aren't available to us. We need to source the setup.bash file from ros sources.

  1. To source our commands, simply run:
source /opt/ros/melodic/setup.bash

Now we are ready to try our container. On the first view of our container, roscore should be already running. On our second view we can try rostopic list to see if we can see /rosout and /ros_agg topics. The expected output should be:

/rosout
/rosout_agg

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Domingos Neto - [email protected]

Project Link: https://github.com/dfvneto/docker_ros

Acknowledgements

  • To my teacher, Cajahyba, who taught me everything that I know about Docker.

About

docker image to use ros:kineitc

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published