-
Notifications
You must be signed in to change notification settings - Fork 370
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
Simulate json output from docker buildx build #1413
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We still use the docker python api to push images, and to run. So we need to set string_output to false, and simulate the json output on buildx. Alternatively we could completely get rid of the python API, but that's a much bigger lift (especially around registry credentials) that I don't want us to do right now. Without this, push progress is reported as raw bytes in the binderhub UI
Is there a simple test that would have caught this? I was able to test manually by running a local registry:
and then pushing to it:
before:
after:
but I'm not sure how to test this practically without launching a local registry for the test. |
minrk
approved these changes
Feb 14, 2025
manics
reviewed
Feb 14, 2025
yuvipanda
added a commit
to yuvipanda/mybinder.org-deploy
that referenced
this pull request
Feb 14, 2025
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
yuvipanda
added a commit
to yuvipanda/mybinder.org-deploy
that referenced
this pull request
Feb 14, 2025
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We still use the docker python api to push images, and to run. So we need to set string_output to false, and simulate the json output on buildx. Alternatively we could completely get rid of the python API, but that's a much bigger lift (especially around registry credentials) that I don't want us to do right now.
Without this, push progress is reported as raw bytes in the binderhub UI