We have gitlab runners on k8s nodes, but recently we have added a rhel 8 node to the cluster.
When running a gitlab runner on this node, we get an error message:
time="2023-03-09T12:18:03.841114832Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc0007ea010, CONNECTING" module=grpc failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: modprobe: can't change directory to '/lib/modules': No such file or directory iptables v1.8.3 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. (exit status 3)
This does not occur on Centos 7 nodes.
Apparently the pipeline is not even started - the dind container fails before becoming ready to run.
We are using this variable on the pipeline:
So it should not be an issue with TLS.
Our setup is the following:
docker 19.3.1 (both on the host and on the dind image)
We’ve tried to launch the dind container manually on the host with a docker build command and it runs fine. Apparently is something related to the gitlab runner itself.
Does anyone know of any issues with rhel / CentOS 8 ?