Questions about kernels created by enterprise_gateway reading data

[yinsen cai]

Hello!

I used enterprise_gateway in kubernetes, and now I have a problem.

When I only used jupyterLab, I mounted data to jupyterLab with Persistent Volume. And when a kernel was started to execute code, as the kernel and the server was on the same node and container, the kernel could read the data with the path such as '/data/input' directly.

However, when I used enterprise_gateway to create kernels in kubernetes, the jupyter server I started and the kernel created by enterprise_gateway might in different nodes. And I mounted my data to jupyter server with Persistent Volume in order to see these data from fronted pages. In this way, when I wanted to execute code with the function of reading data, I used the path just as before such as '/data/input'. And when the kernel started to execute the code, it couldn't find the data with the path, because there was no data on the kernels node.

Is there any suggestions to solve this problem?

Thanks a lot!

[Kevin Bates]

For the others, @kakaluoteasd posted an issue in EG where it can be referenced: https://github.com/jupyter/enterprise_gateway/issues/1008