Infrastructure | CI fails with "The container name ... is already in use by container ..." (#268)

[Ondrej Holy <gitlab-issues gnome org>]

Title: GitLab

Ondrej Holy created an issue:

GitLab CI currently fails for GNOME/gvfs project with the following errors:

Running with gitlab-runner 12.7.1 (003fe500)
  on gcc176-gnome.osuosl.org c13_paMJ
Using Docker executor with image registry.gitlab.gnome.org/gnome/gvfs:latest ...
00:09
WARNING: Container based cache volumes creation is disabled. Will not create volume for "/cache"
ERROR: Preparation failed: Error response from daemon: Conflict. The container name "/runner-c13_paMJ-project-1618-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8" is already in use by container 4be3537226d0ab2fb183e622e6dd0833a30bc2749f55b576f6c0ed65fe1e7342. You have to remove (or rename) that container to be able to reuse that name. (cache_container.go:97:0s)

I have no idea why as I have never seen this earlier and for example pipelines for nautilus works nicely. The privileged tag doesn't help. It seems that "Clear Runner Caches" helped once, but then it has started appearing again and "Clear Runner Caches doesn't work"...

See https://gitlab.gnome.org/GNOME/gvfs/-/jobs/620146.

This is possibly related to https://gitlab.com/gitlab-org/gitlab-runner/issues/4327 and there are mentioned some possible workarounds, but it is weird that it started happening recently as the bug is 2 years old.

Any idea what is wrong?

—
Reply to this email directly or view it on GitLab.
You're receiving this email because of your account on gitlab.gnome.org. If you'd like to receive fewer emails, you can unsubscribe from this thread or adjust your notification settings.