You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reproducing the tutorial only to use 'local' as training_target (with docker installed locally) and data moved to the source directory, so that it is visible to script, I got the following error after the conda environment was built, as a part of the first docker run execution:
Logging experiment running status in history service.
Running: ['docker', 'run', '--name', 'sklearn-mnist_154...b', ...
...
/azureml-envs/azureml_088...6/bin/python: can't open file 'azureml-setup/run_script.py': [Errno 2] No such file or directory
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 4bee4b9a-ce0f-f98b-3160-d6c4a40ef3ac
Version Independent ID: a0475a9e-47f6-2803-8707-fac54ba898dd
Just some additional clarification: I'm running on Windows (Docker for Windows). It seems that the C:\Users...\AppData\Local\Temp\azureml_runs\sklearn-mnist_1546526644_ad63ddfb folder is mounted into \azureml-run but is empty inside the docker image
Problem solved. It had to do with some strange behavior on Docker for Windows, with restrictions to your user password. See more here docker/for-win#25 (comment)
When reproducing the tutorial only to use 'local' as training_target (with docker installed locally) and data moved to the source directory, so that it is visible to script, I got the following error after the conda environment was built, as a part of the first docker run execution:
Logging experiment running status in history service.
Running: ['docker', 'run', '--name', 'sklearn-mnist_154...b', ...
...
/azureml-envs/azureml_088...6/bin/python: can't open file 'azureml-setup/run_script.py': [Errno 2] No such file or directory
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: