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
Bug Description
When I build the image from the repository on windows with this command : docker build . -t slatedocs/slate
Then it will create an error at the moment of run it, regarding this command : docker run --rm --name slate -p 4567:4567 slatedocs/slate serve
Error is: "/usr/bin/env: ‘bash\r’: No such file or directory"
I did try to remove this line from the script "slate.sh" and "deploy.sh" but then I will get this error : "standard_init_linux.go:219: exec user process caused: exec format error"
But if I use the public image, then everything work fine:
docker pull slatedocs/slate
docker run --rm --name slate -p 4567:4567 slatedocs/slate serve
Im on Windows 10 Professionel, version 19042.928
The text was updated successfully, but these errors were encountered:
The same thing happened to me, the initial look points to an issue with the file system that was used to create the files. Specificly an end of line conflict \r for UNIX vs \r\n for windows.
Like yourself, I ended up just using the public image and mounted the source folder as a volume, and carried on.
Bug Description
When I build the image from the repository on windows with this command : docker build . -t slatedocs/slate
Then it will create an error at the moment of run it, regarding this command : docker run --rm --name slate -p 4567:4567 slatedocs/slate serve
Error is: "/usr/bin/env: ‘bash\r’: No such file or directory"
I did try to remove this line from the script "slate.sh" and "deploy.sh" but then I will get this error : "standard_init_linux.go:219: exec user process caused: exec format error"
But if I use the public image, then everything work fine:
docker pull slatedocs/slate
docker run --rm --name slate -p 4567:4567 slatedocs/slate serve
Im on Windows 10 Professionel, version 19042.928
The text was updated successfully, but these errors were encountered: