-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
52 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
title: "Resumen Semana 7" | ||
date: 2024-03-24 | ||
categories: | ||
- Blog (Español) | ||
tags: | ||
- Docker | ||
- RADI | ||
- Nvidia | ||
- GPU | ||
--- | ||
|
||
En esta séptima semana, continué con la tarea de la investigación del problema con el motor de la plataforma, RADI 4, dentro de la plataforma Unibotics. | ||
|
||
Una vez ya estudiado la estructura general y el funcionamiento general del contenedor Docker del motor, he comenzado a revisar la ejecución del motor con más detalle. Para ello, al poder tener acceso al contenedor Docker por dentro, he podido acceder a la terminal nativa del contenedor. | ||
|
||
Dentro de la terminal, ejecuté el programa de Gazebo que utilizan para la simulación del ejercicio manualmente, y en algunos intentos no recibia ningun feedback de la terminal, simplemente no ejecutaba, pero en otros intentos me devolvía dos errores: | ||
|
||
```bash | ||
libegl warning: egl: failed to create dri2 screen | ||
228: invalid egl device | ||
``` | ||
|
||
Al investigar estos errores, me di cuenta que eran errores de exposición de la GPU al contenedor Docker. Entonces al no exponer correctamente la GPU de Nvidia para obtener la aceleración gráfica deseada, el contenedor Docker no se podía comunicar bien con la GPU y no se podía ejecutar correctamente el programa de Gazebo. | ||
|
||
Estos errores se lo he comunicado al equipo de desarrollo para que tuvieran conocimiento. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
title: "Week 7 Overview" | ||
date: 2024-03-24 | ||
categories: | ||
- Blog (English) | ||
tags: | ||
- Docker | ||
- RADI | ||
- Nvidia | ||
- GPU | ||
--- | ||
|
||
During this seventh week, I continued investigating the issue with the platform's engine, RADI 4, within the Unibotics platform. | ||
|
||
After studying the general structure and functionality of the engine's Docker container, I began to review the engine's execution in more detail. By accessing the Docker container internally, I could use the container's native terminal. | ||
|
||
Within the terminal, I manually executed the Gazebo program used for exercise simulation. In some attempts, I received no feedback from the terminal, and the program simply didn't run. However, in other attempts, I encountered two errors: | ||
|
||
```bash | ||
libegl warning: egl: failed to create dri2 screen | ||
228: invalid egl device | ||
``` | ||
|
||
Upon investigating these errors, I realized they were related to the GPU exposure to the Docker container. The issue was that the Nvidia GPU was not properly exposed to achieve the desired graphical acceleration. Consequently, the Docker container couldn't communicate effectively with the GPU, leading to the improper execution of the Gazebo program. | ||
|
||
I have communicated these errors to the development team to make them aware of the issue. |