-
Notifications
You must be signed in to change notification settings - Fork 445
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
[BUG] Cannot build Dockerfile.jupyter #825
Comments
I may have found the issue while trying to run a sparkmagic-powered Jupyter notebook (on my machine, not in a docker container). The jump to |
Answer generated by a 🤖 AnswerI understand that you're encountering an issue when trying to build To address this issue, one potential solution is to downgrade the However, please note that the Here's how you can modify the Dockerfile:
This should allow the Docker image to be built successfully. However, I would recommend checking if this change causes any other issues in your application due to the If you find this solution to be correct and believe that this is a bug that could impact other users, I encourage you to make a pull request with the necessary changes to the Dockerfile. If this solution does not align with your experience, or if you encounter any other issues, I would suggest upgrading to the latest version of sparkmagic and trying again. SourcesThis response is meant to be useful, save you time, and share context. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. |
@agrounds Thanks for reporting this and finding a workaround 🙌 |
Describe the bug
Building
Dockerfile.jupyter
fails with the following error:To Reproduce
git checkout master
docker build . -f Dockerfile.jupyter -t sparkmagic
(replacesparkmagic
with tag of your choosing)Expected behavior
A docker image should be successfully built.
Versions:
9061d05b09d3a224153c223f6ebe4d66019eba28
(master
branch at time of writing)The text was updated successfully, but these errors were encountered: