Line ending problem when using windows for helm

[laurens-jan]

When following the helm/README.md, I'm getting the following error when using could build during building: standard_init_linux.go:195: exec user process caused "no such file or directory"

This is due to the produced docker image not being correct. After investigation, this appears to be a line ending issue.

When converting line endings of all files from a windows line-ending (\r\n) to unix line ending (\n) before calling the gcloud builds submit command, a working image is obtained.

I'm not sure what a correct approach would be to correct this problem, since line endings seem to be dependent on the local git config.

At the very least, this could be mentioned in the helm/README.md

I haven't checked, but the same issue could be present in other community builders.

[MartinFreire]

I had the same problem. Thanks to your question, I try to see if that was the only problem. So I cloned the repo and deploy it on the google cloud shell on the cloud console (a linux environment). It work perfect. I'm leaving this answer here for anyone who came from a google search

[MatteoGioioso]

same issue here standard_init_linux.go:211: exec user process caused "no such file or directory" This happened because I built the image in a Windows environment. I then try to build it in ubuntu and the error has gone