aws / aws/amazon-sagemaker-feedback

Can't Use New Custom Image In Existing Space

Open
#110 2 comments 2 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Product Version

- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio

### Issue Description

I created a new image and attached it to my domain. The image shows as being attached to the domain and I can create a new JupyterLab space and use the image to start and execute commands in a JupyterLab. When I try to use the image in a space created prior to attaching the new image I get an error saying the image is not present in the list of custom images (even though it is).

### Expected Behavior

User should be able to use custom image in existing space

### Observed Behavior

ResourceNotFoundError: Unable to launch App [arn:aws:sagemaker:us-west-2:....] with Image [geospatial] because it is not present in list of custom images in AppSettings. Please update AppSettings to add Image [geospatial] in list of custom images.

image

### Product Category

JupyterLab

### Feedback Category

_No response_

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

No repository files or tests are identified. Start by reproducing the flow with a custom image attached to the domain, comparing a newly created JupyterLab space with an existing space; done means the existing space can launch with that image without the AppSettings error.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, jupyter
Domain
cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.