-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notebook SageMaker_SSH_Notebook.ipynb
fails due to docker-compose
#43
Comments
SageMaker_SSH_Notebook.ipynb
fails due to docker.composeSageMaker_SSH_Notebook.ipynb
fails due to docker-compose
Hi, @djmarti , thanks for bringing up this important observation. The issue is probably rooted in the recent changes of Please, downgrade the version as a workaround:
There's nothing that we can do on the SageMaker SSH Helper side, I'll keep this issue open until SageMaker Notebooks will get an update. |
Thanks Ivan for your prompt response and for the workaround. I think I gave a misleading hint. I am still unable to run the notebook after downgrading
But now I get an error that smells like a permission error:
A permission error is surprising because I didn't have issues before and because there haven't been any changes in my setup. |
Looking into exception stack trace, I see that it's again something related to SageMaker itself rather than to SSH Helper. It's downloading the code from S3, most likely from the default bucket that looks like If the above steps don't help, please, raise a support case: |
Apologies for the long delay. I retried with the exact same code and the problem is gone, which is consistent with your suggestion that this was something related to SageMaker. Everything works as expected, closing the ticket. |
I've faced the similar message with |
The notebook
SageMaker_SSH_Notebook.ipynb
throws an error related to docker compose:Not sure what is causing the error. I was able to run the same notebook content just three months ago. Any hint or suggestion will be greatly appreciated.
The text was updated successfully, but these errors were encountered: