Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEA]: Dockerfile for nvcomp #52

Open
sbates130272 opened this issue Feb 7, 2022 · 3 comments
Open

[FEA]: Dockerfile for nvcomp #52

sbates130272 opened this issue Feb 7, 2022 · 3 comments
Labels
feature request New feature or request inactive-30d inactive-90d
Milestone
2.3

Comments

@sbates130272
Copy link

Add a Dockerfile to the repo to assist in the building of the nvcomp library and benchmarks. Given the interdependencies on gcc, CUDA and distro this would be a useful addition to the repository.

A Dockerfile in a docker subfolder that builds nvcomp (including the extensions).

I'll work up a RFI PR for this for discussion.
sbates130272 added a commit to sbates130272/nvcomp that referenced this issue Feb 7, 2022
@sbates130272
docker/Dockerfile: Create a docker-based way to build nvcomp
ca36e56 
Building and then running nvcomp can be a bit tricky with dependencies
on different versions of cmake and CUDA etc. This commit creates a
Dockerfile which makes it much easier to build the nvcomp library and
benchmarks in a consistent environment. One can then either copy the
files out of the container onto the host or use the nvidia-docker [1]
framework to run programs against GPUs installed on the system.

[1]: https://github.com/NVIDIA/nvidia-docker

Addresses NVIDIA#52.
@sbates130272 sbates130272 mentioned this issue Feb 7, 2022
Draft
@sbates130272 sbates130272 changed the title [FEA] [FEA]: Dockerfile for nvcomp Feb 7, 2022
@sbates130272
Copy link
Author

I submitted a draft PR for this just to get some initial feedback on interest. LMK what you think and I can take the feedback and work on a full PR if there is interest.

@mnicely mnicely added this to the 2.3 milestone Feb 24, 2022
@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature or request inactive-30d inactive-90d
Projects
None yet
Milestone
2.3
Development

No branches or pull requests
2 participants
@sbates130272 @mnicely