You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jet-pilot sets its own variables for python, e.g.:
PYTHONHOME = '/tmp/.mount_jet-piOqe0fr/usr/'\n PYTHONPATH = '/tmp/.mount_jet-piOqe0fr/usr/share/pyshared/:/usr/lib/python3.12
the result is that a kubelogin with azurecli fails with:
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding\nPython runtime state: core initialized\nModuleNotFoundError: No module named 'encodings'
running the command line works just fine from a shell:
kubelogin get-token --login azurecli --server-id xxxx
anything else that can be tried?
The text was updated successfully, but these errors were encountered:
What OS are you using to run JET Pilot? And what installation method did you use?
Afaik JET Pilot does not set any custom variables and quick checks on MacOS have shown no Python vars to be set and we do not use Python under the hood either.
Debug logging / Applications logs are my highest priority at the moment. Probably will be in the next release in the upcoming days. It would be great if you could provide yours once it's out.
jet-pilot sets its own variables for python, e.g.:
PYTHONHOME = '/tmp/.mount_jet-piOqe0fr/usr/'\n PYTHONPATH = '/tmp/.mount_jet-piOqe0fr/usr/share/pyshared/:/usr/lib/python3.12
the result is that a kubelogin with azurecli fails with:
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding\nPython runtime state: core initialized\nModuleNotFoundError: No module named 'encodings'
running the command line works just fine from a shell:
kubelogin get-token --login azurecli --server-id xxxx
anything else that can be tried?
The text was updated successfully, but these errors were encountered: