4 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
I'm experiencing the same error. My image has also been used for months without any problems. It started yesterday.
Also, cloudwatch logs don't show any errors.
As a temporary fix, you can start an instance with a default kernel (data science 3.0) and then switch to your custom image.
beantwortet vor 9 Monaten
0
I have been worked with Sagemaker support and they implemented the changes, the instance should be created correctly with custom images.
during the issue, @Gonzalo's temp solution was working perfectly
beantwortet vor 9 Monaten
0
I also tested running the notebook from "notebook job". Looks like the kernel from job scheduler can start kernel without custom image without error.
beantwortet vor 9 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
Thanks, this works :)
But for some instance type (by default, only allow 1 running app per domain), I cannot use this way to switch because after I created one by default kernel, it won't let you create second one with custom image.
Hope Sagemaker team notice this issue and implement the fix asap.