We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The entrypoint script for the containers is executed with monitor mode enabled (using -m flag), eg. here https://github.com/aws/sagemaker-pytorch-container/blob/97e611b4cb2df13d966d508e56d1c990439b2163/docker/1.3.1/py3/Dockerfile.gpu#L166
This prints the following message at the start of any sagemaker job that uses the container:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell
Removing the -m flag gets rid of this message. Is there a particular reason for using this flag? If not we should remove it from all Dockerfiles.
The text was updated successfully, but these errors were encountered:
thanks for bringing this to our attention! I have reached out to the responsible team for insight.
Sorry, something went wrong.
Same issue here. Any update?
The Dockerfiles have actually since been moved to https://github.com/aws/deep-learning-containers - would you mind opening up a new issue in that repository?
No branches or pull requests
The entrypoint script for the containers is executed with monitor mode enabled (using -m flag), eg. here https://github.com/aws/sagemaker-pytorch-container/blob/97e611b4cb2df13d966d508e56d1c990439b2163/docker/1.3.1/py3/Dockerfile.gpu#L166
This prints the following message at the start of any sagemaker job that uses the container:
Removing the -m flag gets rid of this message. Is there a particular reason for using this flag? If not we should remove it from all Dockerfiles.
The text was updated successfully, but these errors were encountered: