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
Investigate notebook container sidecar to enable in-notebook container builds #312
Comments
On further investigation this seems to be a lower priority than experimenting with simply sharing code via NFS or another means and avoiding the need to build a new image for each training run. |
Duplicate of #192 |
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Nov 1, 2019
…" (kubeflow#312) This reverts commit 76bd875.
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Feb 15, 2021
* add bestTrialId to statusJob status * generate mock and add bestworkerid
elenzio9
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Oct 31, 2022
* Adding James to google-kubeflow-admins.members.txt * Add chesu and fix order
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The issue of how best to build training images is an open question, see #300, #289
At first take it looks like this could be done from a JupyterHub notebook by attaching a Docker daemon sidecar, configured via KubeSpawner, similar to this.
@yuvipanda Do you see any problems with this approach?
The text was updated successfully, but these errors were encountered: