I am trying t connection bro run jupyter notebook on an EC2 instance, following your advice here. It works fine, but since for something more long-running, theeaks sometimes, I decided to also use screen:
ssh -i -L 8889:localhost:8888
conda activate gluon
When I now open any notebook, none of the dependencies in the gluon environment are there. In fact, I don’t think the notebook is using the env.
If I do not use screen [just remove the $ screen above], things work fine, but then I have the problem with the connection breaking things.