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

exit status 2: iptables v1.8.7 (nf_tables): Couldn't load match `conntrack' #86

Open
jhderojasUVa opened this issue Jan 3, 2023 · 0 comments

Comments

@jhderojasUVa
Copy link

There's an error on WSL2 of concourse/concourse:latest image that can be related on: https://dev.to/lemosluan/comment/1nmi7

The image (web, concourse/concourse) is not running giving this error on the log:

{"timestamp":"2023-01-03T08:38:44.584522300Z","level":"error","source":"quickstart","message":"quickstart.worker-runner.logging-runner-exited","data":{"error":"Exit trace for group:\ngarden exited with error: Exit trace for group:\ncontainerd-garden-backend exited with error: setup host network failed: appending accept rule for RELATED \u0026 ESTABLISHED connections failed: running [/usr/sbin/iptables -t filter -A CONCOURSE-OPERATOR -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT --wait]: exit status 2: iptables v1.8.7 (nf_tables): Couldn't load match `conntrack':No such file or directory\n\nTry `iptables -h' or 'iptables --help' for more information.\n\ncontainerd exited with nil\n\nhealthcheck exited with nil\ndebug exited with nil\nvolume-sweeper exited with nil\ncontainer-sweeper exited with nil\nbaggageclaim exited with nil\nbeacon exited with nil\n","session":"2"}}

At microsoft/WSL#7948 (comment) says that can be solved by, on the Dockerfile setting:

sudo update-alternatives --set iptables /usr/sbin/iptables-legacy

So using iptables-legacy

Previous versions (6.X) works correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant