-
Notifications
You must be signed in to change notification settings - Fork 565
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
Can't find Dockerfile as client on Windows #589
Comments
@trane9991 try with |
@fsouza
Conclusion: |
@fsouza P.S. I tried to replace |
@fsouza Does this bug still exist in the library? If so, you would be willing to implement the work-around that @trane9991 mentioned? It would be nice to get https://github.com/dnephin/dobi working on Windows. |
This is also causing a problem in Harbur Captain on Windows. I have opened a bug there (harbur/captain#77) but it seems a fix here would be the correct solution. |
I apologize for leaving this bug hanging for so long. I just pushed a tentative fix. Unfortunately I don't have a Windows host where I can reproduce the bug nor test the fix, but the CI build did succeed: https://ci.appveyor.com/project/fsouza/go-dockerclient/build/355. @jward-2ndwatch can you give it a shot? |
I will try to make some time and give it a shot soon. Thanks for getting to this. |
@fsouza I rebuilt Harbur Captain with this update and it looks like it solved the issue I was having. 👍 |
@jward-2ndwatch thank you very much for confirming! |
Hello,
using client connecting to remote docker daemon.
When connecting from Linux to Docker daemon installed on CoreOS everything is ok.
When connecting from Windows to Docker daemon installed on CoreOS and trying to build docker image(on remote system) I get
API error (500): {\"message\":\"Cannot locate specified Dockerfile: Dockerfile\"}
. Pull images works ok.where is:
app.cnf.DockerfilesPath = "images"
anditem.Name = app1
Dockerfile is located in the:
images/app1/Dockerfile
Building on remote docker daemon from client on Linux passes, and failing on Windows...
Any ideas why?
The text was updated successfully, but these errors were encountered: