Open bzheng06 opened 4 months ago
@bzheng06 Thanks for reaching out to sagemaker! Ideally users are not required to handle any delete/create network for local mode. The issue you are encountering seems to be coming from docker-compose, and seems to be due to the network creation not handled by docker compose itself.
It seems the work around you mentioned is the expected path forward really. Is there a use-case why you needed to delete/create the "sagemaker-local" network as a pre-step here?
@mufaddal-rohawala I opened up a PR with the bug fix right here if you'd like to take a look: https://github.com/aws/sagemaker-python-sdk/pull/4699
Describe the bug Running the ScriptProcessor in local mode on either a desktop or notebook instance results in a RuntimeError when it reaches the 'docker compose up' command.
To reproduce First run commands: docker network rm sagemaker-local docker network create sagemaker-local
Just running 'docker rm sagemaker-local' and then the code in local mode is a workaround for the issue as of now.
Expected behavior For the script processing job to run and output properly.
Screenshots or logs
System information A description of your system. Please provide:
Additional context Add any other context about the problem here.