This repository has been archived by the owner on Jun 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
nvidia docker v2 support #93
Labels
enhancement
New feature or request
Comments
@koenlek thank you for your suggestion, sounds nice. |
2 tasks
@amc-nu : I made the PR a couple of days ago. Please go ahead and let me know if its ok like this. |
Thanks @koenlek, I'll check it soon. |
2 tasks
frank770504
referenced
this issue
in frank770504/compal_kinetic_ros_docker
Dec 2, 2018
source is found in below link https://github.com/CPFL/Autoware/issues/1161
Hi, You can simply just docker pull the image for testing docker pull twbabyduck/autoware:1.9.1-kinetic-opengl |
I found somebody do a similar thing at autowarefoundation/autoware#1946. Mouri |
frank770504
referenced
this issue
in frank770504/compal_kinetic_ros_docker
Aug 26, 2019
source is found in below link https://github.com/CPFL/Autoware/issues/1161
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add nvidia docker v2 support
A couple of months ago, nvidia released nvidia-docker v2. As it turned out, this broke OpenGL within docker containers when using nvidia GPU. This means that tools like RVIZ wouldn't work anymore when using nvidia docker v2. Luckily, they provides a fix by now, which needs to be inserted into the docker image. Such a patched version works fine again with nvidia, but (at least for me) doesn't seem to work anymore with e.g. Intel GPU acceleration. So, for now, our company resorted to providing two image tags alway: 1 for nvidia, 1 for intel.
To patch an existing docker image, use this Dockerfile:
For Autoware, you need to take care of the user too, so it would become:
To build:
Then to run, all you need to do is change your docker run command to something like:
Could you add support for this directly from Autoware?
The text was updated successfully, but these errors were encountered: