Mirantis / Mirantis/cri-dockerd
Running with "no-op" network plugin tries to run Linux command on Windows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
If you run cri-dockerd on Windows with --network-plugin no-op, it will print the following:
level=error msg="can't set sysctl bridge-nf-call-iptables: open /proc/sys/net/bridge/bridge-nf-call-iptables: The system cannot find the path specified."
Looking at the source code, I see it also tries to run a modprobe br-netfilter regardless of the host OS.
The error isn't fatal, but even so, these commands probably shouldn't be executed on Windows in the first place.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the handling of the --network-plugin no-op option and trace where the sysctl write and modprobe br-netfilter command are invoked. Verify the Linux behavior remains unchanged while Windows does not attempt either command, then run the relevant existing tests if the source identifies them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100