At step #5 sha256sum "no such file or directory" caused by linefeed compatability

[bunnybooboo]

Wow thanks for this awesome work. Exactly what I needed today. I've recently switched to Windows after almost a decade solely in Linux. Stepped into Windows 11 beta channel test this week. This project is the first Docker setup I've tried in this fresh instance.

In this new setup there seems to be an interoperability issue surrounding linefeeds in the old Unix vs Windows battle for how to do things right. When the dockerfile hit sha256sum checks across the packages it spits out an error no such file or directory. Might be dense of me but, you know, a decade's some time hey.

The only way I could resolve it to proceed with the build was to use the following in GIT config command before cloning this repo:
git config --global core.autocrlf false

A heads-up for you as it could go a little way to improving the documentation in your README for anyone not already tweaked GIT in this way and spare them a headache. Build just completed WAHOOOO!

[skeeto]

Thanks for pointing this out. I've always disabled CRLF conversion, so I didn't know it was an issue. Then suddenly two of you trip over it a day apart (see #9). I've added a .gitattributes to disable line ending conversion, so that should fix it in future checkouts. This Git "feature" drives me nuts.