Closed akhileshekartha closed 6 months ago
Looks like the problem is with creating an image.
You can try two things:
add -imageName ""
to the Run-AlPipeline
Clean up your docker filesystem using this method: https://freddysblog.com/2018/12/11/clean-up-after-yourself-docker-your-mom-isnt-here/
and let me know if this works.
Thanks
Thanks for your fast response. I ran the Docker cleanup script, but it didn't fix the problem. The same error kept happening. Then, I modified the script by adding -imageName ""
, and that resolved the issue.
Sorry about the confusion. For another project, the Run-AlPipeline worked fine on Docker versions BC23 and BC25 on the same docker machine. I mistakenly thought there was a problem with the version BC20 image.
I have seen an increasingly number of people, where creating images fails. Not sure why this is - but it seems to be docker / host related. Setting imageName to blank means that it skips the image creation and just creates the container directly.
Hi , I'm not sure if it's related to the Microsoft image, but it was operating till yesterday and only started throwing this error this morning, while other projects, including the BC23 version, were running normally on the same Docker machine.
Thanks for the info - I will keep this in mind if I see more of this
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue BcContainerHelper Version 6.0.15 Error hitting BC Run-AlPipeline for BC 20.0.37253.38230/nz
DockerDo : re-exec error: exit status 1: output: hcsshim::ImportLayer failed in Win32: The system cannot find the path specified. (0x3)
Scripts used to create container and cause the issue
Full output of scripts
Screenshots If applicable, add screenshots to help explain your problem.