-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 error with varnish and manager #1
Comments
I got the same error! need helps |
I do not use docker with Windows so I can't test this at the moment. I just pulled and rebuilt with docker running in Ubuntu and everything starts up and installs as expected. It's worth mentioning the manager is intended for production, you can comment it out completely to skip building and running it. If I get a chance to test under Windows I will let you know.... |
Thank you fast answer! So u think is more easy to develop on linux os, right? |
I always use Ubuntu for my hosting so it makes sense for me for dev and staging servers to be as near to production as possible so I work with Windows and Mac OS but use VMWare to create Ubuntu instances where I do all my main development for Magento. |
I will try and I let know if it works. Thanks again |
Closing this as inactive. |
I think it does not work @squalonero @gaiterjones |
Update docker-compose to docker compose
The reason for this error is because when you clone this repo with Git under Windows, the default setting for Git is to replace the Unix LF line endings to CR LF. This shell will not understand that. So the solution is to save the file with Unix line endings and to run |
Thanks @MarcoMiltenburg for this fix. |
Oh and the same goes for the file |
After running
docker-compose up -d
manager and varnish look "turned off" in docker, with following logs:
Manager:
standard_init_linux.go:211: exec user process caused "no such file or directory"
Varnish:
/bin/sh: 1: /usr/bin/varnish-start.sh: not found
If I skip and go through, I can install magento but host does not respond.
The text was updated successfully, but these errors were encountered: