Rather simple fix for this, need to make sure the CI job is using an image that contains the docker cli executable. Edit your .gitlab-ci.yml and make sure you have:
image: docker:latest
From this post.
GitLab Runner with Docker executor: “client version 1.43 is too old”
Setting up a Docker image build in my GitLab ci I got this error:
ERROR: Error response from daemon: client version 1.43 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version: driver not connecting
Docker version on the VM running the GitLab Runner:
$ docker --version
Docker version 29.1.3, build f52814d
Versions in my .gitlab-ci.yml:
image: docker:24.0.5-cli services: - docker:24.0.5-dind
Updated both to match the Docker version on the VM resolved the issue.
gitlab-runner unable to pull repos (host not found)
I’ve set up a new gitlab-runner on my homelab GitLab server. It’s using a Docker executer, and when it attempts to pull the repo to build, it’s gets error:
Could not resolve host: gitlab.local (Domain name not found)
gitlab.local is in /etc/hosts on the VM and I can ping the name and it resolves. A quick Google found this post, and the suggestion is to edit /etc/gitlab-runner/config.toml and add:
network_mode = "host"
to the [runners.docker] section. Seems like that fixes the issue.
k3s nodes showing not ready after initial install and config
‘kubectrl describe nodes’ is showing
reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
for each node.
This looks like the same issue as here – I followed the quickstart guide and used the ‘--flannel-backend none' option which looks like I setup a snigle node cluster with no networking…
Following the network docs here, I changed my setup line removing the ‘none’ option and now everything is good:
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="server" sh -s - --token [my token]