-
Notifications
You must be signed in to change notification settings - Fork 2k
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
network: bridge: iptables seems not to support comments #9837
Comments
Hello @haai! That's a bit of a surprise. It looks like from the log message here that the comment is being added in the CNI library. So we'll need to open an issue with upstream for that. That being said, can you run |
hi @tgross. thanks for your reply. Yes thats right .. I was curious also about this and checked the cni plugins repository. The plugins set the comments. But nomad passes the comments to the plugins also with UUIDs. Here for example: https://github.com/containernetworking/plugins/blob/master/plugins/main/bridge/bridge.go#L615
I was thinking, when the comments are not being added by the plugin will nomad then continue to work or are these UUIDs in the comment does have any meaning, for bookkeeping e.g.? Unfortunately the exact command does not work on my node. They have all modules in just
|
Yes, but that's expected by the interface we're calling into.
Right, the snippet you linked to is a good example of what they're used for: after the allocation has finished, we need to be able to clean up the iptables entry and the only way to "ID" an entry is via the comment.
Ok, the This is definitely an unusual kernel build for a server; I might not build a server with a preemptible kernel but presumably the Synology folks had some specific in mind. You may want to try using host networking first to verify that everything else is working. But at that point I think you're going to need to add kernel modules to get bridge networking working; I'm not sure how feasible that is with this kind of appliance. |
Thx @tgross for your answer :) |
It's definitely not ideal. Fortunately because this is Linux the appliance vendor should be making their kernel tree available, and your kernel build config should be available at something like (And we probably should have some documentation around what minimal set of kernel features is required for bridge networking support, but I'm not totally sure about how stable those requirements are.)
That's my understanding. I'm going to tag @nickethier and @shoenig just to double-check me, but I don't think there's a way around that. |
To use Consul Connect with sidecar proxies, yes CNI plugins + bridge networking is required. You could make use of Consul Connect Native to get around that requirement, but that requires using a connect library in your app, which may not be practical or possible. |
I'm going to close this as it's a matter of dependencies on the kernel build. |
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.12.4 (8efaee4ba5e9727ab323aaba2ac91c2d7b572d84)
Operating system and Environment details
Linux srv 4.4.59+ #25426 SMP PREEMPT Wed Jul 8 03:21:29 CST 2020 x86_64 GNU/Linux synology_apollolake_918+
iptables version is v1.6.0
Issue
I have here a specific problem. I am trying to run nomad scheduler on my synology NAS and it seems that the iptables does not support comments. The bridge has been created and also other ip tables and rules but on the below rule an error is thrown in the job.
Reproduction steps
Having a synology disk station :) or iptables without comments extension and creating job with
Job file (if appropriate)
Nomad Client logs (if appropriate)
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: