K
Q

Gitlab Runner fails with ERROR: Job failed (system failure): Internal error occurred: connection reset by peer

5/26/2019

I get this error from time to time when running builds with my dedicated runners, running on GKE.

What could be the problem here? Is it related to the Gitlab instance or is it more a problem on the cluster side?

ERROR: Job failed (system failure): Internal error occurred: error executing command in container: error during connect: Get http://%!F(MISSING)var%!F(MISSING)run%!F(MISSING)docker.sock/v1.27/exec/f9ee0d021b8a6d7660d2334456a93f61108835077574545bcf00a484b45f5247/json: read unix @->/var/run/docker.sock: read: connection reset by peer

-- Tim Schwalbe
docker
gitlab
google-kubernetes-engine

Similar Questions

What is the best practice for service discovery on the application layer in Kubernetes?
Error validating data: ValidationError(PersistentVolume.spec) with Helm
How does Kubernetes control replication?
Nginx on Kubernetes (99: Cannot assign requested address)
How to deploy keycloak as a pod in kubernetes dashboard which is set up up in AWS EC2?
K8S Get deployment liveness probe status
Pods are stuck at ContainerCreating after deletion of the pod
Changing the Deployment Strategy from RollingUpdate to Recreate using Golang
How to view kubernetes api traffic with wireshark
kubernetes error: the server doesn't have a resource type "jenkins"
K3s node keeps failing and I’m not sure what is causing it
how to show swagger ui for kubernetes api?

1 Answer

9/25/2019

See the same thing randomly. There are some jobs more likely than others to trigger it but a retry usually works fine

-- Seer
Source: StackOverflow