-
Notifications
You must be signed in to change notification settings - Fork 3
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
Provide setup instructions for installing binderhub-service #72
Conversation
Partial livestream of me trying out and making this PR here: https://www.youtube.com/watch?v=WMymAqFd6mQ |
93b7555
to
db54e93
Compare
98db189
to
dc22ee0
Compare
Worked through these with @simaattar2003 and made these changes. Co-authored-by: simaattar2003 <[email protected]>
9dfee02
to
51915c8
Compare
a417e8e
to
0afa27d
Compare
for more information, see https://pre-commit.ci
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.
Thank you for writing these @yuvipanda!!!
For reference, some related content:
- there are some development setup notes at Live notes towards a test deployment and demo #19 (comment)
- Testing of build/push is done in our CI system as well, where we use
curl
which can end with a success message rather than failed to launch:
binderhub-service/.github/workflows/test-chart.yaml
Lines 195 to 197 in b2a3c43
- name: Test image build/push via binderhub REST API using curl run: | curl http://localhost:30080/build/gh/binderhub-ci-repos/cached-minimal-dockerfile/HEAD?build_only=true
10. Let's verify that _image building and pushing_ works. Access the binderhub pod by following the | ||
same instructions as step 3. But this time, you should see a binderhub page very similar to that | ||
on [mybinder.org](https://mybinder.org). You can test build a repository here - I recommend trying | ||
out `binder-examples/requirements`. It might take a while to build, but you should be able to see | ||
logs in the UI. It should succeed at _pushing_ the github image, but will fail to launch. The last | ||
lines in the log in the UI should look like: | ||
|
||
``` | ||
Successfully pushed europe-west10-docker.pkg.dev/binderhub-service-development/bh-service-test/binderbinder-2dexamples-2drequirements-55ab5c:50533eb470ee6c24e872043d30b2fee463d6943fBuilt image, launching... | ||
Launching server... | ||
Launch attempt 1 failed, retrying... | ||
Launch attempt 2 failed, retrying... | ||
``` | ||
|
||
You can also go back to the Google Artifact Registry repository you created earlier to verify that the built | ||
image is indeed there. | ||
|
||
11. Now that we have verified this is working, we can disable the binderhub UI as we will not be using it. | ||
Remove the `config.BinderHub.enable_api_only_mode` configuration from the binderhub config, and redeploy | ||
using the command from step 9. |
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.
This is acceptable as it is. An alternative test can be to do:
# this is the test from the github workflow testing things as well btw
curl http://localhost:8585/build/gh/binderhub-ci-repos/cached-minimal-dockerfile/HEAD?build_only=true
I think I'd favor use of curl
as it highlights this is the role of binderhub-service now - API level access to build/push to be consumed by non-binderhub provided UI.
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.
I'd like to keep this one as is for now, hope that's ok.
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.
I also spent today with Sima working on how to connect a JupyterHub to this, and I believe the GUI check 'flows' much better.
Co-authored-by: Erik Sundell <[email protected]>
Thanks, @consideRatio! |
No description provided.