-
Notifications
You must be signed in to change notification settings - Fork 806
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
Minikube guide leads to a hub pod crashloop trying to open database file #3310
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Hi, please can you open a support issue on our community forum, as this may be an issue with your config or your minikube setup: https://discourse.jupyter.org/ Please provide enough information to reproduce your issue, including your config and your full debug logs. Thanks! |
Hi there @ammarar 👋! I closed this issue because it was labelled as a support question. Please help us organize discussion by posting this on the https://discourse.jupyter.org/ forum. If it's your first time posting Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other. Thanks you for being an active member of our community! ❤️ |
Bug description
Running the Jupyterhub installation guide in minikube produces this error:
error.txt
How to reproduce
Example:
Expected behaviour
Step 4 in doc says that you should have pods in Running state
Actual behaviour
The hub pod is in
CrashLoopBackOff
and when I see the logs, it shows the following error:error.txt
Your personal set up
Full environment
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered: