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 trunk tries to execute '/sbin/ip route' which fails on CoreOS #2696

Closed
kmalec opened this issue Jun 7, 2017 · 3 comments
Closed

Nomad trunk tries to execute '/sbin/ip route' which fails on CoreOS #2696

kmalec opened this issue Jun 7, 2017 · 3 comments

Comments

@kmalec
Copy link
Contributor

kmalec commented Jun 7, 2017

Nomad version

Output from nomad version
Nomad v0.6.0-dev (67cd5154bb0add222f1d4dc56283ff9f47a5ec8f+CHANGES)

Operating system and Environment details

Container Linux by CoreOS stable (1353.8.0)

Issue

Nomad in 0.6 branch tries to execute /sbin/ip route during startup, which fails on CoreOS, because they have iproute2 in /usr/bin/ip.
This doesn't happen on 0.5.6; apparently recent change to use github.com/hashicorp/go-sockaddr

Reproduction steps

Compile nomad from trunk and try to run:
nomad agent -server -data-dir /data/nomad-server/data/ -config /data/nomad-server/config/ -region eu-west -dc eu-west-1

Nomad Server logs (if appropriate)

Jun 07 19:32:01 ip-10-249-200-172 systemd[1]: Started Nomad server.
Jun 07 19:32:01 ip-10-249-200-172 nomad[22507]: No configuration loaded from /data/nomad-server/config
Jun 07 19:32:01 ip-10-249-200-172 nomad[22507]: ==> Failed to parse HTTP advertise address: Unable to parse default advertise address: Unable to parse address template "{{ GetPrivateIP }}": unable to execute sockaddr input "{{ GetPrivateIP }}": template: sockaddr.Parse:1:3: executing "sockaddr.Parse" at <GetPrivateIP>: error calling GetPrivateIP: fork/exec /sbin/ip: no such file or directory
Jun 07 19:32:01 ip-10-249-200-172 systemd[1]: nomad-server.service: Main process exited, code=exited, status=1/FAILURE
Jun 07 19:32:01 ip-10-249-200-172 systemd[1]: nomad-server.service: Unit entered failed state.
Jun 07 19:32:01 ip-10-249-200-172 systemd[1]: nomad-server.service: Failed with result 'exit-code'.
Jun 07 19:32:06 ip-10-249-200-172 systemd[1]: nomad-server.service: Service hold-off time over, scheduling restart.
Jun 07 19:32:06 ip-10-249-200-172 systemd[1]: Stopped Nomad server.

Nomad Client logs (if appropriate)

N/A

Job file (if appropriate)

N/A

@dadgar
Copy link
Contributor

dadgar commented Jun 8, 2017

@kmalec Can you file and cross link an issue against that project.

@kmalec
Copy link
Contributor Author

kmalec commented Jun 9, 2017

Did that. Recompiled Nomad with changing that path to /usr/bin/ip for extra CoreOS build, works (as expected).

@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 12, 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

2 participants