I had the same problem after trying everything and getting no helpful info from the aws support other than 'open a support ticket'???? I figured it out myself.
(& Yes it is absolutely a bug on the aws side! It is caused by the missing image)
First find your DomainId you can find it on the UI or do aws sagemaker list-domains
you will see an output like below. It will list CustomImages associated with that sagemaker domain. & status will likely be in a failed state.
Save your output settings just in case!
(I redacted ids with $$$)
{
"DomainArn": "arn:aws:sagemaker:$quot;,
"DomainId": "$$",
"DomainName": "$quot;,
...
"Status": "Update_Failed",
...
"FailureReason": "ResourceNotFoundError: Image with ARN arn:aws:sagemaker:$$ does not exist",
...
"KernelGatewayAppSettings": {
"CustomImages": [
{
"ImageName": "my_custom_image", # this is the image causing problem, you might have more images listed below
"ImageVersionNumber": 1,
"AppImageConfigName": "app-image-config-1"
}
]
}
}
...
}
Create a file update-domain-input.json update the CustomImages list remove the problematic image (but keep others if you have any)
{
"DomainId": DOMAIN_ID,
"DefaultUserSettings": {
"KernelGatewayAppSettings": {
"CustomImages": [
#... add your custom images here (remove the problematic one)
# If you have no images you can just pass an empty array then add image from dashboard UI(easier)
]
}
}
}
now the error should disappear and you should be able to add any image from the UI.(or If you know the config settings for the image you want to add you can do it during the update-domain step above.)
I pieced together this solution looking at this example
You'll have to attach new image versions to SageMaker images before you attach them to the domain. On the left nav under SageMaker dashboard -> Images, you should be seeing a list of images. Create new versions here and you'll then be able to attach these to the domain.
I provide an alternative solution. You can create an image by choosing any image from your ecr and name it as the missing image. Then it would be visible on your sagemaker console, you can ignoreit or delete it. For me this was the only solution because my roll was not allowed to execute a UpdateDomain action.
发布评论
评论（3）
尝试了所有内容后，我也遇到了同样的问题，除了“打开支持票”
I had the same problem after trying everything and getting no helpful info from the aws support other than 'open a support ticket'????
I figured it out myself.
(& Yes it is absolutely a bug on the aws side! It is caused by the missing image)
First find your
DomainIdyou can find it on the UI or do
aws sagemaker list-domainsGet your domains current settings:
aws sagemaker describe-domain --domain-id $DOMAIN_IDyou will see an output like below.
It will list
CustomImagesassociated with that sagemaker domain. & status will likely be in a failed state.Save your output settings just in case!
(I redacted ids with $$$)
Create a file
update-domain-input.jsonupdate theCustomImageslist remove the problematic image (but keep others if you have any)aws --region ${REGION} sagemaker update-domain --cli-input-json file://update-domain-input.jsonnow the error should disappear and you should be able to add any image from the UI.(or If you know the config settings for the image you want to add you can do it during the update-domain step above.)
I pieced together this solution looking at this example
在将新图像版本附加到域上，您必须将新图像版本附加到域上。在萨台制造商仪表板下方的左导航板上 - ＆gt;图像，您应该看到图像列表。在此处创建新版本，然后您将可以将它们附加到域上。
You'll have to attach new image versions to SageMaker images before you attach them to the domain. On the left nav under SageMaker dashboard -> Images, you should be seeing a list of images. Create new versions here and you'll then be able to attach these to the domain.
我提供了另一种解决方案。
您可以通过从ECR中选择任何图像并将其命名为缺失图像来创建图像。然后，它可以在您的SageMaker控制台上可见，您可以忽略或删除它。
对我来说，这是唯一的解决方案，因为不允许我的滚动执行更新域操作。
I provide an alternative solution.
You can create an image by choosing any image from your ecr and name it as the missing image. Then it would be visible on your sagemaker console, you can ignoreit or delete it.
For me this was the only solution because my roll was not allowed to execute a UpdateDomain action.