-
Notifications
You must be signed in to change notification settings - Fork 1
Feat: Enable CUDA-enabled images and multi-arch builds #106
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.
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
Conversation
run-image/Dockerfile
Outdated
| ARG cnb_uid=1001 | ||
| ARG cnb_gid=1001 | ||
| ENV CNB_USER_ID=${cnb_uid} | ||
| ENV CNB_GROUP_ID=${cnb_gid} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I understand that the user id during the build phase is 1001, we should keep user 1000:1000 for when we run the image.
4d2acf0 to
1cfd725
Compare
leafty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some minor questions:
run-image/Dockerfile
Outdated
| ENV CNB_USER_ID=${cnb_run_uid} | ||
| ENV CNB_GROUP_ID=${cnb_run_gid} | ||
|
|
||
| RUN |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Empty run?
run-image/Dockerfile
Outdated
|
|
||
| USER $user_id | ||
| WORKDIR /home/renku | ||
| RUN (userdel $(getent passwd ${cnb_uid}|cut -d: -f1) || true) && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also delete the groups 1000 and 1001 if they exist?
leafty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
This PR introduces significant enhancements to our Dockerfile and build process, allowing for the seamless integration of CUDA-enabled images and improving multi-architecture support.
The core changes involve updating the Dockerfile to support using a single image as both a build image for our builder and as a runtime image. This refactoring streamlines our image management and ensures consistency across different stages of the build and deployment pipeline.
To facilitate these changes, several new dependencies have been added. These additions are crucial for Paketo's Python buildpack, as they provide the necessary tools and libraries for successfully building Python applications within the updated environment. This ensures that our Python projects continue to build correctly while leveraging the new image capabilities.
With these updates, we can now utilize CUDA-enabled images, opening up possibilities for accelerated computing tasks within our environments.