114532 Views
101685 Views
86270 Views
54891 Views
51137 Views
49962 Views
Level Up your CAD Skills
Operation Pico
Raspberry Pi Home Hub
Hacky Temperature and Humidity Sensor
Robot Makers Almanac
High Five Bot
Using the Raspberry Pi Pico's Built-in Temperature Sensor
Getting Started with SQL
Introduction to the Linux Command Line on Raspberry Pi OS
How to install MicroPython
Wall Drawing Robot Tutorial
BrachioGraph Tutorial
KevsRobots Learning Platform
75% Percent Complete
By Kevin McAleer, 3 Minutes
To get the ROS visualisation tool rviz2 to work in our docker container we need to redirect any graphics calls to outside our container into the hosts’s X11 environment.
rviz2
X11 is a software package developed by the Massachusetts Institute of Technology (MIT) in the 1980s that enables graphical user interfaces (GUIs) to be created and used on Unix-based systems. It works by using a network protocol called the X Window System Protocol to communicate between the server and the client. The server is responsible for managing the user interface, while the client is responsible for displaying the user interface. The X11 protocol is used to send commands from the server to the client, which are then interpreted by the client and used to generate the output.
X11
X11 is used by many popular operating systems, including Linux, Mac OS X, and Windows.
To redirect any X11 display commnds from within the docker container runnign ROS2, to outside the container (our Raspberry Pi 4 OS), we need to do two things:
xhost
export
DISPLAY
xhost local:root
environment: - display
The full docker-compose.yml file should now look like this:
version: "3.9" services: ros2: build: . network_mode: host volumes: - /home/kev/ros:/home/ros - /home/kev/cubie-1:/ros2 devices: - /dev/ttyUSB0:/dev/ttyUSB0 tty: true environment: - DISPLAY
Now that we have updated our docker-compose file we need to bring the new container online; docker-compose has a simple command for this called up:
up
docker-compose up -d
Note the -d parameter means run the container disconected. If you don’t include this, the terminal will run the container and all the container output will display on this terminal, but it will also quick should the terminal session end.
-d
< Previous Next >