-
Notifications
You must be signed in to change notification settings - Fork 31
Simplify and optimize Docker image #264
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
Conversation
for more information, see https://pre-commit.ci
@edoardob90 do you need a review on this? I could give a hand. |
If you want, you can try to build the container from the Dockerfile. I tested the workflow in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @edoardob90, I did a first pass and I would need some clarifications from your side.
707acaf
to
3786be6
Compare
Options: Leave the
|
@yakutovicha I think we need to resume/finalize this. It would simplify a lot the build step of the image, and solve the recent problem with the workflow run that, all of a sudden, ran out of disk space on the hosted runner. If we're deploying only on Renkulab, the |
* Trigger build for PR, but only when from the same repo * Multi-arch build * Uses "docker/metadata" action to set up labels and tags
* Keep only branch, pr, and SHA * Add repo tags vX.Y or vX.Y.Z
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, grazie @edoardob90!
jupyter-repo2docker
dependencydocker/environment.yml
The old workflow has been renamed to
.github/workflows/repo2docker.yml
and Binder is still supported via thebinder/
directory (unchanged).Also: since Docker provides already the isolation, there's no need to have another virtual environment. All the tutorial dependencies are installed in the
base
environment, which is automatically configured by the base image.