Skip to content
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

nomad agent -dev fails on Windows #295

Closed
ChrisHines opened this issue Oct 16, 2015 · 5 comments
Closed

nomad agent -dev fails on Windows #295

ChrisHines opened this issue Oct 16, 2015 · 5 comments

Comments

@ChrisHines
Copy link
Contributor

OS: Windows Server 2012 R2 Standard
ARCH: amd64

C:\>nomad version
Nomad v0.1.2

C:\>nomad agent -dev
==> Starting Nomad agent...
2015/10/16 13:02:05 [ERR] fingerprint.env_aws: Error querying AWS Metadata URL, skipping
==> Error starting agent: client setup failed: driver setup failed: Get http://unix.sock/version: dial unix /var/run/docker.sock: socket: An address incompatible with the requested protocol was used.
@dadgar
Copy link
Contributor

dadgar commented Oct 16, 2015

PR #225 should fix that issue. This has not made it into one of our pre-compiled binaries however. Let me know if it still doesn't work on HEAD.

@ChrisHines
Copy link
Contributor Author

Yes, I am just getting started with the pre-compiled binaries and didn't see a previous issue about this.

I won't be able to test HEAD until I get Nomad building from source.

@ChrisHines
Copy link
Contributor Author

I have built nomad from source:

C:\gopath>go get -u github.com/hashicorp/nomad

C:\gopath\src\github.com\hashicorp\nomad>git describe --always
v0.1.2-173-g29ce6e0

After copying the resulting binary to the server it still doesn't work, but it gives a different error now:

D:\nomad>nomad agent -dev
==> Starting Nomad agent...
2015/10/16 15:37:22 [ERR] fingerprint.env_aws: Error querying AWS Metadata URL, skipping
==> Error starting agent: client setup failed: driver setup failed: Get http://127.0.0.1:2375/version: dial tcp 127.0.0.1:2375: connectex: No connection could be made because the target machine actively refused it.

@cbednarski
Copy link
Contributor

@ChrisHines When the driver fails to fingerprint it should simply deactivate. This failure scenario seems to be happening a bit differently on Windows. We'll get this fixed up. Thanks for the report!

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants