1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi there!
The reason you're seeing this behaviour is the underlying EC2 instance that runs JupyterLab gets terminated when you stop the notebook instance.
You can utilise lifecycle configuration script which is a bash script that runs when the EC2 instance spins back up, in this script, you can re-install extensions so your environment can be set-up properly when you open JupyterLab.
Below links provide examples on how to achieve this:
https://docs.aws.amazon.com/sagemaker/latest/dg/notebook-lifecycle-config.html
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un mois
- demandé il y a un an
- demandé il y a un an
- demandé il y a 3 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 mois