aws-samples / aws-samples/sagemaker-run-notebook
Lifecycle configuration failure
- Dominant language
- Python
- Stars
- 144
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
Created a new domain SageMaker Studio domain today. I can install the run-notebook extension in studio if I run the commands of the `install-run-notebook.sh` script myself in a studio lab terminal.
However, when I add that script as a Lifecycle configuration following instructions provided in this repo I can't start studio as it keeps cycling back to a "restart server" screen. When I do click to restart on that screen, a couple of minutes pass and it comes back to the same screen. I had colleagues test it as well and it was the same for them.
UPDATE: Wanted to update this post to say I just noticed in my new SageMaker Domain the new "Notebook Jobs" feature which seems to integrate sageMaker-run-notebook directly into the SageMaker Studio UI. I tested it and it accomplishes what I was using the library for. Therefore this issue is no longer of high importance to me, but I did want to raise the issue in case someone else is spending time on this.
Also, thank you for making this awesome Jupyter Extension and tooling! I was raving to people about it last year, so couldn't be more pleased to see it is now integrated into SageMaker.
Contributor guide
Research direction
The report concerns install-run-notebook.sh used as a SageMaker Studio lifecycle configuration; start by reading that script and the repository's lifecycle-configuration instructions. Reproduce the restart loop and compare it with manual terminal execution; done means identifying a reproducible cause or documenting the configuration failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, jupyter, python
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100