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.

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

Closed
cwbeitel opened this issue Feb 28, 2018 · 3 comments
Closed

Comments

@cwbeitel
Copy link
Contributor

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?

@cwbeitel
Copy link
Contributor Author

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.

@jlewi
Copy link
Contributor

jlewi commented Mar 1, 2018

Building Docker images from Jupyter and sharing code from NFS are orthogonal.

Issue #192 is discussing how to build Docker images from Jupyter. Closing this issue in favor of that one.

Duplicate of #192

@jlewi jlewi closed this as completed Mar 1, 2018
@jlewi
Copy link
Contributor

jlewi commented Mar 1, 2018

Duplicate of #192

@jlewi jlewi marked this as a duplicate of #192 Mar 1, 2018
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Nov 1, 2019
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants