After switching machines and reinstall problem with starting RIVZ

[vllxkxs]

Thanks for creating an issue, we will support you as soon as possible.
Please fill out the issue template below by answering all questions.
Providing as much information as possible will help us to solve the problem as fast as possible!

1. Are you using a virtual machine or are you using native Ubuntu?

Native Debian

2. If you are using macOS and a virtual machine, does your computer use an M1, M2, ... chip? "Does not apply" if the question does not apply to you.

Does not apply

3. Which Ubuntu version are you using? (lsb_release -a in a terminal)

Kali-Rolling but Docker for Bullseye

4. On your host, in a terminal, navigate to the acdc repository and execute ls -la and paste the content here.

drwxrwxr-x 9 lukas lukas 4096 22. Jan 08:18 .
drwxrwxr-x 3 lukas lukas 4096 22. Jan 08:18 ..
drwxrwxr-x 2 lukas lukas 4096 22. Jan 08:18 assets
drwxrwxr-x 2 lukas lukas 4096 22. Jan 08:18 bag
drwxrwxr-x 3 lukas lukas 4096 22. Jan 08:18 catkin_workspace
drwxrwxr-x 3 lukas lukas 4096 22. Jan 08:18 colcon_workspace
drwxrwxr-x 2 lukas lukas 4096 22. Jan 08:50 docker
drwxrwxr-x 9 lukas lukas 4096 22. Jan 08:18 .git
drwxrwxr-x 4 lukas lukas 4096 22. Jan 08:18 .github
-rwxrwxr-x 1 lukas lukas 2761 22. Jan 08:18 .gitignore
-rwxrwxr-x 1 lukas lukas 2001 22. Jan 08:18 .gitlab-ci.yml
-rwxrwxr-x 1 lukas lukas 833 22. Jan 08:18 .gitmodules
-rwxrwxr-x 1 lukas lukas 1104 22. Jan 08:18 LICENSE
-rwxrwxr-x 1 lukas lukas 2816 22. Jan 08:18 README.md

5. On your host, in a terminal, navigate to the catkin_workspace folder in the acdc repository and execute ls -la and paste the content here.

drwxrwxr-x 9 lukas lukas 4096 22. Jan 08:18 .
drwxrwxr-x 3 lukas lukas 4096 22. Jan 08:18 ..
drwxrwxr-x 2 lukas lukas 4096 22. Jan 08:18 assets
drwxrwxr-x 2 lukas lukas 4096 22. Jan 08:18 bag
drwxrwxr-x 3 lukas lukas 4096 22. Jan 08:18 catkin_workspace
drwxrwxr-x 3 lukas lukas 4096 22. Jan 08:18 colcon_workspace
drwxrwxr-x 2 lukas lukas 4096 22. Jan 08:50 docker
drwxrwxr-x 9 lukas lukas 4096 22. Jan 08:18 .git
drwxrwxr-x 4 lukas lukas 4096 22. Jan 08:18 .github
-rwxrwxr-x 1 lukas lukas 2761 22. Jan 08:18 .gitignore
-rwxrwxr-x 1 lukas lukas 2001 22. Jan 08:18 .gitlab-ci.yml
-rwxrwxr-x 1 lukas lukas 833 22. Jan 08:18 .gitmodules
-rwxrwxr-x 1 lukas lukas 1104 22. Jan 08:18 LICENSE
-rwxrwxr-x 1 lukas lukas 2816 22. Jan 08:18 README.md

6. On your host, execute docker images and paste the content here.

hello-world latest 74cc54e27dc4 8 hours ago 10.1kB
rwthika/acdc ros1 b4c4c4abd17a 15 months ago 23.8GB

7. Briefly explain your problem here. The explanation should contain a description of the expected behavior and the actual behavior.

I switched machines recently. Thus I wanted to reinstall the necessary tools for the ACDC course. Since Docker is not supported for Rolling yet, I found that the version for Bullseye was compatible. The installation worked only with minor problems and docker is running correctly. Up on testing the provided docker image for this course I found that when trying to open an empty GUI window, I had some issues with the MESA-loader - quite similar to the problem mentioned in the troubleshooting section (There is a screenshot below showing the exact error messages). Thus I replaced the script with the changes recommended in the trouble shooting section of the edX guide. With this change, this worked flawlessly. However, I am unable to test RVIZ. In some cases I am unable to execute roscore correctly and get flooded with restarts. In other cases this happens afterwards when executing rviz. Therefore I am unable to open any proper RVIZ window/instance.

8. If you got an error message, paste it here or post a screenshot of it.

Error Message:

[rosout-1] process has died [pid 247, exit code -6, cmd /opt/ros/noetic/lib/rosout/rosout __name:=rosout __log:=/root/.ros/log/f8f910c2-d898-11ef-a6fd-0242ac110002/rosout-1.log].
log file: /root/.ros/log/f8f910c2-d898-11ef-a6fd-0242ac110002/rosout-1*.log

NOTE: There are several of these messages but obviously with changing pid!

Screenshot:

[TillBeemelmanns]

Hi,

after a quick search I found that people mount -v/dev/dri:/dev/dri folder into the container for Debian and bullseye setups.

• Libgl error with amdgpu flatpak/flatpak#3875

Can you please try that ?

Best,
Till

[vllxkxs]

Hi,

Thank you for your quick response! I have added the folder to the setup of the docker/script. It looks like this now:

#!/bin/bash

in order to be able to use this script install:

pip install docker-run-cli

DIR="$(cd -P "$(dirname "$0")" && pwd)"
if docker ps --format '{{.Names}}' | grep -q "acdc_ros1"; then
docker-run --name acdc_ros1
else
docker-run --no-gpu
--volume $(dirname "$DIR"):/home/rosuser/ws
--network host -v/tmp/.X11-unix:/tmp/.X11-unix -v/dev/dri:/dev/dri
--image rwthika/acdc:ros1
--workdir="/home/rosuser/ws/catkin_workspace"
--name acdc_ros1
fi

This removes any error message when starting an empty GUI window. However, when trying to execute roscore I am facing the described issues where multiple processes throw std::bad_alloc. There is a screenshot attached in the original ticket. In case you need any further information please let me know!

With kind regards

Lukas

[TillBeemelmanns]

Hi,

okay we solved the GUI problem.

Now we still have the problem launching roscore. I suspect that there is something wrong with the network setup using Debian/Bullseye and docker-run. docker-run only supports Ubuntu. Unfortunately, I do not have a setup like yours to reproduce the problem. I would suggest you to create a minimal reproducible error using native docker run command and a ros noetic image.

E.g.

docker run -it  rwthika/acdc:ros1 bash

Inside the container

roscore

Does the same error appear in this case ? If not, then there might be a problem with docker-run.

Best,
Till

[vllxkxs]

Hi,

the error did disappear in that case. Hence I got help with properly fixing the docker-run command which solved the issue.

Thanks a lot for your time and help!

Kind regards,
Lukas