-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Networking seems broken when using exec driver. #1123
Comments
It does use host networking. Can you try running it in raw exec. Looks like it is a DNS resolution error. |
I did run it on the host and it worked well. |
@c4milo Thanks for reporting. Will look into it, my guess is that the resolv.conf file is not in the chroot. |
It would be very helpful if Nomad provided an easy way of entering a container to further inspect when issues like this show up. |
@c4milo if you are using th exec driver you can use the nomad fs suite of commands to introspect the file system of the chroot. |
I had something different in mind, like being able to run one-off containers, attached to the terminal. To run for example db migrations, test networking, test container isolation, etc. |
@c4milo Can you please tell us if this has been resolved, and if resolv.conf is present in the chroot? |
Last time I checked, yes, I was still experiencing the issue. I couldn't check if resolv.conf was present, I changed strategy and ended up writing a custom driver because of this issue and several other custom needs. |
@c4milo We have recently merged #1518 which would allow you to specify the host directories you want in your chroot so please configure the Closing the ticket, please re-open the ticket if that doesn't solve your needs. |
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. |
Nomad version
Nomad v0.3.2-rc2 ('8411b0b3bc167dde5d0edc20220266609d6d93bb')
Operating system and Environment details
CoreOS stable
Issue
I'm trying to launch Vault using exec driver but it fails trying to resolve a domain name.
Reproduction steps
Just try to launch Vault using the exec driver on CoreOS, ideally on AWS using IAM roles, and a similar configuration to the following:
Job file
Desired result
I was expecting the exec driver to use the host's network stack.
The text was updated successfully, but these errors were encountered: