-
Notifications
You must be signed in to change notification settings - Fork 32
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
Document running the RAPIDS Notebooks container as a Snowpark Service #419
Comments
I looked a bit more into this, and it looks like the steps are pretty much what's detailed. Couple of notes and things to figure out are: Here is a walkthrough video that also covers part of the rpocess: https://youtu.be/izeG3pvvy9M?list=PLavJpcg8cl1GN7AwaY95PXqwUw4qj8zLo&t=411
TODO:
TODO:
For what I could gather from the demos, it seems like you build the image locally and then push it to the container registry. I was hoping one would be able to pull from let's say dockerhub or similar directly into snowpark registry but I can't find docs on that. Which it might be a bit limiting for a doc example
From the demo docs steps are the image is build locally and they use snowpark CLI + docker to push it to the registry.
This should be almost identical to the process here https://quickstarts.snowflake.com/guide/intro_to_snowpark_container_services/#3 except some rapids caveats that we will find out.
Do we need to create a snowflake table then, is there any snowflake table we can "copy"? what do we have in mind here? |
Closed by #493 |
The Snowflake documentation has an example of running a container with Jupyter in as a service in Snowpark and accessing the Jupyter UI via a Service endpoint.
It would be great to add a documentation page that walks through the same steps but using the RAPIDS notebooks container on a GPU compute pool.
I imagine the steps will be something along the lines of:
The text was updated successfully, but these errors were encountered: