- Newest
- Most votes
- Most comments
It's not enough to have the AppImageConfig locally and only push the built image to ECR -- you also need to push the AppImageConfig using the following command:
aws sagemaker create-app-image-config \
--cli-input-json file://app-image-config-input.json
And then use that when you're attaching the custom image to the SageMaker domain.
If you're doing that in the Console, then you don't actually use the AppImageConfig file itself -- you just enter the info from it into the create image dialog:
"MountPath": "/root",
"DefaultUid": 0,
"DefaultGid": 0
"Name": "python3",
"DisplayName": "Python [conda env: myenv]"
I used the UI to attach image to domain. The image url i took from https://docs.aws.amazon.com/deep-learning-containers/latest/devguide/dlc-base-cu128-x86-ec2.html
But then, in jupyter lab, when i ran the space with newly created image, it gave below error.
ResourceNotFoundError: SageMaker is unable to launch the app using the image xyz]. Ensure that the UID/GID provided in the AppImageConfig matches the default UID/GID defined in the image.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
