We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As an Analytical Platform engineer I want one single base image for tooling that contains common software So that we keep our codebases DRY
Our VS Code does not use a COTS image, rather we build it from scratch, adding in tools like AWS CLI, Miniconda and NVIDIA drivers.
As we start to rebuilt JupyterLab and RStudio, they will also be packaged with this software and we'll have to maintain it in three places
@jacobwoffenden
Analytical Platform Engineering
If we create a common tooling image Then we can just layer IDEs on top
Create a common tooling base image with:
No response
The text was updated successfully, but these errors were encountered:
jacobwoffenden
No branches or pull requests
User Story
As an Analytical Platform engineer
I want one single base image for tooling that contains common software
So that we keep our codebases DRY
Value / Purpose
Our VS Code does not use a COTS image, rather we build it from scratch, adding in tools like AWS CLI, Miniconda and NVIDIA drivers.
As we start to rebuilt JupyterLab and RStudio, they will also be packaged with this software and we'll have to maintain it in three places
Useful Contacts
@jacobwoffenden
User Types
Analytical Platform Engineering
Hypothesis
If we create a common tooling image
Then we can just layer IDEs on top
Proposal
Create a common tooling base image with:
Additional Information
No response
Definition of Done
The text was updated successfully, but these errors were encountered: