-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
airbyte-ci: use a new cache volume for docker cache #42905
airbyte-ci: use a new cache volume for docker cache #42905
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on Graphite |
b883a07
to
c171e0e
Compare
This reverts commit c171e0e.
2e5b876
to
69121ed
Compare
@@ -41,7 +41,7 @@ | |||
DOCKER_CLI_IMAGE = f"docker:{DOCKER_VERSION}-cli" | |||
DOCKER_REGISTRY_MIRROR_URL = os.getenv("DOCKER_REGISTRY_MIRROR_URL") | |||
DOCKER_REGISTRY_ADDRESS = "docker.io" | |||
DOCKER_VAR_LIB_VOLUME_NAME = "docker-cache" | |||
DOCKER_VAR_LIB_VOLUME_NAME = "docker-cache-2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we in the position where we should make a directory per day, so that this self heals?
What
It appears that the cache volume we use to cache
/var/lib/docker
on the side car docker engine was corrupted.It led to failure of integration test run for java connectors (cf thread here)
I can't identify what let to the cache volume corruption but using a fresh volume (by renaming the volume name) fixes the testing problem.