-
Notifications
You must be signed in to change notification settings - Fork 928
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
How to correlate gcr.io version tag with GitHub commit? #532
Comments
It looks like the v51 was built on March 12th (the v50 on Feb 21st). Do you have a simple way to reproduce the bug with (To respond to your question, we don't have a public way to correlate versions and commits) |
Thank you. I was hoping to see I cannot repro the bug running the image from the command line. Running The problem I have is that I use JupyterHub and, within that, Docker Spawner. As such, the hub spawns this image. This is where it fails and there are no helpful error messages. I suspect that there is a conflict between my version of JupyterHub and the Kaggle Dockerfile. My :
:
c.JupyterHub.spawner_class = 'dockerspawner.DockerSpawner'
c.DockerSpawner.remove_containers = True
c.DockerSpawner.image_whitelist = {
'Data Science (Python)': 'kagglepython'
}
:
: where I can successfully run
That single user run works for |
Hi, I am having an issue with the latest
gcr.io/kaggle-images/python
integration with JupyterHub (I posted this question in the Kaggle Forums). I can getv50
to work, but notv51
. How do I correlate the commits in this repo to thegcr.io
version tag so I can do a diff and see what changed? Thanks.The text was updated successfully, but these errors were encountered: