-
Notifications
You must be signed in to change notification settings - Fork 62
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
Support network bridge mode #36
Comments
due to this change it does not seem possible to use consul connect with the podman driver |
@maartenbeeckmans Have you been able to use podman and connect? I'm only facing missing drivers issue whenever I use podman with connect. |
I was not able to use it, tried to modify the example by setting the task driver to podman and the sidecar_task.driver to podman but had several issues. Biggest issue was the support for bridge mode on group level instead of task level, which is a requirement for consul connect iirc. |
I struggled too with making this example work. Everything is correctly set up because if I use the docker driver it works but not when I use Podman (which is correctly working for regular jobs). |
If I didn't miss anything this should be / is supported (or did you get any error messages related to this or is it documented somewhere?).
And the "Features" section even claims that Consul Connect is supported (which conflicts with this issue and my experience - at least in terms of a practical setup):
However, it currently seems to be broken because the loopback interface ("lo") doesn't get initizlized properly. This bug is tracked via hashicorp/nomad#10014 and affects at least the "exec" and "podman" drivers. There are two hacky workarounds though:
That should be because of the following:
This uses the Docker driver by default:
The default Envoy task is equivalent to the configuration shown here: https://www.nomadproject.io/docs/job-specification/sidecar_task#default-envoy-configuration The solution is to use the following:
However, in addition to the aforementioned issue with the loopback interface, I hit two more issues when using the Envoy image with Podman through Nomad:
Anyway, the tl;dr is that I cannot recommend trying to get Consul Connect working with the "podman" (or "exec") driver at this point. It should be possible (I at least managed to get it working with the "exec" driver) but it isn't pretty/practical at all. The most important blocker is hashicorp/nomad#10014. And after that the Envoy container image needs to be improved to work with SELinux+Nomad+Podman (but IIRC it was working fine without Nomad (i.e., SELinux+Podman) so this might rather need fixes in |
@primeos-work Tagged you in a comment on a dicuss.hashicorp thread as well. Sorry if that's annoying.
Just to be sure, are you saying that it's not worthwhile to try and use the |
No, I was just saying that IMO the Nomad + Podman + Consul Connect seemed too much trouble at the time to use it (especially in production). Now, with hashicorp/nomad#10014 resolved, it should be fine(-ish). I guess we can close this issue too now? I did at least manage to get the Consul Connect demo working with the |
Huh, weird. In the situation referenced in that discuss.hashicorp post, I could not do anything network-based in the exec task. Do you have an example set of configs you could send my way? |
Also running into the same driver issue when trying to use consul as the service provider. |
You need to grab the sidecar_task block here and change the driver to Podman. Consul connec and bridge on a group works for me in the latest Nomad versions on Rocky 9. |
Hi folks, starting with Nomad v1.6 (and a So far things look good with ubuntu 22.04 and podman v3.4.4. I still need to verify the RHEL and podman 4 side of things. If there are additional issues we can track them in the ticket above. I believe hashicorp/nomad#13428 / hashicorp/nomad#10014 resolved the PS - Thanks to everyone who has helped by investigating or fixing issues - this driver has been a monumental community effort and wouldn't be possible without ya'll! |
Only with Nomad v1.6 it works? |
Driver currently supports
bridge
network mode via task config but not from a driver and task group perspective.Support the connect demo
The text was updated successfully, but these errors were encountered: