If you have some experience with programming you know how complicated and error prone setup of new dev environment can be, especially if you are using technologies, without built-in package management system (for instance pip or NuGet), like C or C++. When you add more and more dependencies to your project it can be really tough to move it around and onboard new developer to your team.
Imagine that you can pack every dependency into some kind of bag, open it basically everywhere and focus on coding instead of installing everything from scratch. To achieve above we will utilize Docker containers and VSCode with officially created by Microsoft Remote Containers extension.
- CUDA-enabled host device
- Familiarity with CMake
- Remote containers VSCode Extension
- Nvidia container toolkit
Remote container setup
First of all, to develop CUDA-enabled application you need proper device with CUDA support and installed Nvidia container toolkit to be able to use Nvidia’s GPU from container. After installing all requirements on your host computer, you can proceed to creation of remote container configuration and finally project.
Right after creating root directory for new project you should create
.devcontainer directory, next create
devcontainer.json file inside.
Created in previous step
devcontainer.json is used to communicate with remote containers extension which handles all docker related actions for you.
You’re almost there, now put into
devcontainer.json content below:
// you have to pass what gpu you wan to CUDA interact with
// add capacity and security-opt to enable debugging inside container
// list contains of all extensions that will be always available inside container
Once above configuration is ready you can jump into container by selecting
Reopen in container option from command palette (
Ctrl + Shift + P) or by clicking in green button in bottom left corner of the VSCode window.
After window reload you can test your setup by typing
nvidia-smi into terminal, expect output to look like this:
When you are sure that container with CUDA is up and running you can start shaping solution. There are many approaches to manage building, testing and packaging but in this tutorial will be used CMake, de facto industry standard, portable and well documented tool from company named Kitware. It’s good to use appropriate tools to solve problems it saves your time and makes your life easier, so if you have never used it I highly recommend to get familiar with CMake by reading great introduction available here.
Once you have your
CMakeLists.txt files ready adding CUDA can be done in multiple ways utilizing modern CMake.
If your projects always requires CUDA use:
LANGUAGES CUDA CXX)
or use code below if CUDA is optional:
Now you can select your kit (Clang for instance), configure, build and run your project with CUDA on board. Happy codding inside container!
Using this knowledge you can go deep and experiment with: