-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
MNT: Check if running inside repo2docker more explicitly #30835
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
.dockerenv is only supported in the old docker based builder, which has been deprecated for a few years now. It isn't supported by buildkit / docker buildx, which repo2docker *just* moved to (jupyterhub/repo2docker#1402). Using buikdkit gives us faster and more reliable builds. This converts the test for checking if the script is being run by repo2docker to check for an env var that repo2docker sets instead.
I missed your comment earlier, @lesteve! Responded in #30697 (comment) :) |
Brings in: repo2docker (among others): - jupyterhub/repo2docker#1402 - jupyterhub/repo2docker#1413 binderhub: - jupyterhub/binderhub#1929 - jupyterhub/binderhub#1930 Note that this *could* cause some issues for the very few repos that depend on internal details of the non buildx old builder. For example, see scikit-learn/scikit-learn#30835
Brings in: repo2docker (among others): - jupyterhub/repo2docker#1402 - jupyterhub/repo2docker#1413 binderhub: - jupyterhub/binderhub#1929 - jupyterhub/binderhub#1930 Note that this *could* cause some issues for the very few repos that depend on internal details of the non buildx old builder. For example, see scikit-learn/scikit-learn#30835 We also remove memory limits, as those are not supported right now via the docker buildx build. We will need to add support for custom buildkit builders in binderhub, and then we can use those.
This will break scikit-learn on binder once jupyterhub/mybinder.org-deploy#3225 lands, which is very soon. Also note i'm using scikit-learn as one of the repos i smoke test before significant mybinder deploys :) |
The change has been deployed, and this PR is now needed for the mybinder link to work. |
Thanks for the PR and glad to know that scikit-learn is amongst your smoke test repo 🙏! I am trying to kick off a mybinder build using this URL: and I am getting an error (maybe this is already known?):
|
It seems like the mybinder error has already been reported in Zulip. |
Side-comment: CI failure is unrelated to this PR, see #30761. This will likely go away with another push. |
I set auto-merge, so this will be merged automatically when CI is green! Thanks @yuvipanda for the PR! |
ty @lesteve :) Yeah, as we bump back to doing more work on mybinder.org, i think there'll be momentary instability. However, this is from my perspective a different kind of instability - caused by us actually moving, getting stronger and more resilient than from not :) Is fixed now, and i see scikit-learn launches fine. |
…n#30835) Co-authored-by: Loïc Estève <loic.esteve@ymail.com>
.dockerenv is only supported in the old docker based builder, which has been deprecated for a few years now. It isn't supported by buildkit / docker buildx, which repo2docker just moved to (jupyterhub/repo2docker#1402). Using buikdkit gives us faster and more reliable builds.
This converts the test for checking if the script is being run by repo2docker to check for an env var that repo2docker sets instead.