Gitlab auto devops build fail when pushing image to registry

Summary

Gitlab autodevops build fail when pushing image to registry.

image

I'm using digital ocean kubernetes cluster. 2 other repositories use the same kubernetes cluster and same gitlab runner, but only one repository suffer from this problem and idk how to solve it.

Steps to reproduce

Use gitlab runner on digital ocean kubernetes cluster

Example Project

Repository is private, can't do that

What is the current bug behavior?

error creating overlay mount to /var/lib/docker/overlay2/e9c1e89d2c5304fb0e8f1676640a2e8a8c252600fb9e8eedf7c785d0064b00b1/merged: device or resource busy

What is the expected correct behavior?

Image pushed to registry, build succeed.

Relevant logs and/or screenshots

Link to logs

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Possible fixes

Edited Oct 27, 2019 by numfin
Assignee Loading
Time tracking Loading