Healthcheck failed - requires API version 1.41, but the Docker daemon API version is 1.40

Hi,

I’m running on the shared runners on gitlab.com. But since a few minutes I get this error when running with a dind as service:

Health check error:

[12](https://gitlab.com/[someproject]/services/api-user/-/jobs/5958445292#L12)create service container: "specify container image platform" requires API version 1.41, but the Docker daemon API version is 1.40 (services.go:192:0s)

Originally I was using docker:dind for the service. But now I’ve tried to use another dind version, even those which are described in the docs. But to no success. It seems that there is someing strange.

Does anyone know how to fix it?

Same issue here.

aiting for services to be up and running (timeout 30 seconds)...
*** WARNING: Service runner-xs6vzpvo-project-40121291-concurrent-0-1958299fd35dd94d-docker-0 probably didn't start properly.
Health check error:
create service container: "specify container image platform" requires API version 1.41, but the Docker daemon API version is 1.40 (services.go:192:0s)
Service container logs:
2024-01-18T12:54:59.808967103Z cat: can't open '/proc/net/arp_tables_names': No such file or directory
2024-01-18T12:54:59.813568533Z ip: can't find device 'nf_tables'
2024-01-18T12:54:59.814741460Z modprobe: can't change directory to '/lib/modules': No such file or directory

Yes, it’s the same.
I’ve tried it with diffrent versions of docker:dind and docker:cli (24.0.5, up to rc) but with no success.

Hi everyone, we’re aware of the issue (due to a Runner update we rolled out earlier), a rollback is already in progress.

Hi, I have came across the same issue - Unable to build docker images on shared runners - it prevents any docker image to be built. It seems like Gitlab team noticed this already and checking internally.

Thanks! Please get back to us when the issue is resolved.

Best,

FYI - You can follow incident issue in 2024-01-18: DIND not working in Shared Runners after update (#17422) · Issues · GitLab.com / GitLab Infrastructure Team / production · GitLab and track its status, and on GitLab System Status

FYI - operational again. Sorry for the inconvenience, and thanks for reporting.