Conversation
8f09ffd to
82d5ab7
Compare
|
I've also changed the Jupyter Dockerfile to install dask directly into the root environment used by the Jupyter notebook server by default. |
|
I had a bit of trouble building the jupyter docker image because of its reliance on If I copy over the prepare.sh script explicitly then I can do the following and everything works as expected |
|
I used |
|
|
||
| ENTRYPOINT ["/usr/local/bin/dumb-init", "--"] | ||
| CMD ["bash", "-c", "/usr/bin/prepare.sh && exec dask-scheduler"] | ||
| ENTRYPOINT ["/usr/local/bin/dumb-init", "bash", "/usr/bin/prepare.sh"] |
There was a problem hiding this comment.
Yes, this is definitely the solution to free the CMD that you mention in #4 i didn't do this initially because it would make it impossible to skip the prepare.sh but in general its not a big issue i think.
| cytoolz ipywidgets \ | ||
| && conda clean -tipsy | ||
| ENV PATH=/opt/conda/envs/dask/bin:$PATH | ||
| RUN jupyter labextension install @jupyter-widgets/jupyterlab-manager |
|
What's your publication mechanism? Just build locally and push to dockerhub? |
Yes |
|
Actually nevermind, I did setup up the two images on dockerhub so they will get automatically build from new commits on master. |
|
Grand. OK to merge? |
|
yes. lgtm |
|
Thank you for your help @danielfrg !
…On Sat, Dec 2, 2017 at 9:27 PM, Daniel Rodriguez ***@***.***> wrote:
yes. lgtm
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AASszB67LKKqEJHFMbDaKFzeq1j8LF9Xks5s8gcIgaJpZM4QzcJc>
.
|
See #4 and helm/charts#2912
cc @danielfrg also @ogrisel