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
Jupyter pod can't start; jinja exception Encountered unknown tag 'trans'. #325
Comments
In stack driver I used the following filter to get the logs
I see a jinja error
|
|
Here's the super relavant bit Jinja is giving the following error
which appears to be coming from this piece of Jupyter code
|
It looks like this was added ~8 months ago as part of preliminary I18n support to Jupyter /cc @JCEmmons |
/cc @ojarjur |
I've been hitting this too. My Docker builds from yesterday were picking up version 5.0.0 of the notebook package, but today they've started picking up version 5.4.0. Right now I'm experimenting with pinning to different versions to see if the problem will go away. |
When I look at the files in the image |
I looked at the hub pod and I find trans tags in the file |
Notebook recently started being localizable, and this seems related. I suspect some installation setup somehow that has the template files from a newer version of notebook than the code. Are you mixing conda and pip for the notebook package? Conda / pip mixing feels like the most likely culprit |
Yeah looks like we're mixing conda and pip |
Rebuilt the image and the new one works; gcr.io/kubeflow-images-staging/tensorflow-notebook-cpu:v20180301-1838-pr317-1932b26-f88d" I think my previous build might not have been a clean build. |
I tried spawning a notebook with the Jupyter notebook image
gcr.io/kubeflow-images-staging/tensorflow-notebook-cpu:v20180301-pr317
The pod appears to start and is killed right away. Looks like Jupyter reaps the pod right away making it difficult to debug.
I managed to run
kubectl describe pods
while it was still running and this is what I saw.Looks like Jupyter exited as soon as it started.
The text was updated successfully, but these errors were encountered: