Summary
Error initializing network controller when running airbyte-ci connectors command in Docker via WSL2 + Ubuntu
Question
Hey all! Trying to run airbyte-ci connectors --name=source-quickbooks build to test some connector updates and I’m getting the error:
failed to start daemon: Error initializing network controller: error obtaining controller instance: unable to add return rule in DOCKER-ISOLATION-STAGE-1 chain: (iptables failed: iptables --wait -A DOCKER-ISOLATION-STAGE-1 -j RETURN: iptables v1.8.10 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain DOCKER-ISOLATION-STAGE-1
Any thoughts? I’ve already tried the suggestions of sudo update-alternatives --set iptables /usr/sbin/iptables-legacy that I’ve seen in a few threads. Running Airbyte on Docker via WSL2 + Ubuntu.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.
Join the conversation on Slack
["error", "airbyte-ci-connectors", "docker", "wsl2", "ubuntu"]
Just checking back in here - <@U02TQLBLDU4> <@U069EMNRPA4> any ideas? I’ve gone through several more iterations of reinstalling, changing configs, etc. and currently blocked from customizing this connector as far as I can tell.
Unfortunately I don’t have much idea, not familiar with limitations of running Docker on Windows. In MacOS/Ubuntu the commands works like a charm
If it helps, I am running it through Ubuntu on Windows.
Hey <@U02TQLBLDU4>! Docker is running on my machine. Output from docker ps is:
7c0e6affa606 <http://registry.dagger.io/engine:v0.9.6|registry.dagger.io/engine:v0.9.6> "dagger-entrypoint.s…" 43 hours ago Up 2 minutes dagger-engine-81cc306759c2da0f
cb0e4eef0f4b airbyte/proxy:0.57.4 "./run.sh ./run.sh" 43 hours ago Up 33 seconds 0.0.0.0:8000-8001->8000-8001/tcp, :::8000-8001->8000-8001/tcp, 0.0.0.0:8003->8003/tcp, :::8003->8003/tcp, 80/tcp, 0.0.0.0:8006->8006/tcp, :::8006->8006/tcp airbyte-proxy
6cccbfe4ce9b airbyte/connector-builder-server:0.57.4 "/bin/bash -c airbyt…" 43 hours ago Up 33 seconds 0.0.0.0:32770->8080/tcp, :::32770->8080/tcp airbyte-connector-builder-server
fd6ae57921f2 airbyte/webapp:0.57.4 "/docker-entrypoint.…" 43 hours ago Up 33 seconds 8080/tcp airbyte-webapp
e1ca4d922414 airbyte/worker:0.57.4 "/bin/bash -c airbyt…" 43 hours ago Up 33 seconds 5005/tcp, 0.0.0.0:32772->9000/tcp, :::32772->9000/tcp airbyte-worker
d9091af445a5 airbyte/cron:0.57.4 "/bin/bash -c airbyt…" 43 hours ago Up 33 seconds airbyte-cron
9a10b12985cc airbyte/server:0.57.4 "/bin/bash -c airbyt…" 43 hours ago Up 33 seconds 5005/tcp, 8000/tcp, 0.0.0.0:32769->8001/tcp, :::32769->8001/tcp airbyte-server
f34dc7263d9d airbyte/airbyte-api-server:0.57.4 "/bin/bash -c airbyt…" 43 hours ago Up 33 seconds 5005/tcp, 0.0.0.0:32771->8006/tcp, :::32771->8006/tcp airbyte-api-server
77669d64e3f7 airbyte/db:0.57.4 "docker-entrypoint.s…" 43 hours ago Up 45 seconds 5432/tcp airbyte-db
9d221aec438b airbyte/temporal:0.57.4 "./update-and-start-…" 43 hours ago Up 45 seconds 6933-6935/tcp, 6939/tcp, 7233-7235/tcp, 7239/tcp airbyte-temporal
e53861f5fb6d alpine/socat "socat -t 900 TCP-LI…" 43 hours ago Up 45 seconds 0.0.0.0:32768->2375/tcp, :::32768->2375/tcp airbyte-docker-proxy-1```
I’ve also run into this exact issue that <@U06UL827N9M> mentioned
Hey <@U02TQLBLDU4>, just checking in here. Any thoughts on what the issue could be?
Is docker running in your machine? What is the output of docker ps
This looks to me a lot like it’s not Airbyte-specific problem, but the word Windows is a little bit suspicious to me. If you’re in WSL —perhaps try running on a completely un-windowsed Linux WM. Either something local or a VM on AWS / GCP or anything else should do.