You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a data scientist / ML engineer, I do not want to go through the overhead of downloading all sorts of dependencies and uploading them back to the internet as a container image, before I can sub my job for execution (since I am on a limited-bandwidth connection).
Instead, I want these container images to be built on a build server, according to the image specification given as part of my job metadata.
This approach yields additional benefits:
Improved caching (esp. in teams), since images don't need to be built multiple times on each team members' local machine
No architecture gap (e.g., macOS/Linux, ARM/x64) between clients and compute server
No need for data scientists to install container tooling on their machine
Potential for security measures on the build server (e.g., vulnerability scanning, image signing, SBOM, ...)
The text was updated successfully, but these errors were encountered:
As a data scientist / ML engineer, I do not want to go through the overhead of downloading all sorts of dependencies and uploading them back to the internet as a container image, before I can sub my job for execution (since I am on a limited-bandwidth connection).
Instead, I want these container images to be built on a build server, according to the image specification given as part of my job metadata.
This approach yields additional benefits:
The text was updated successfully, but these errors were encountered: