From 494054ce5a917bcca0ef062a76ba4aa0a051aa75 Mon Sep 17 00:00:00 2001 From: Dennis Felsing Date: Tue, 28 Nov 2023 16:41:11 +0000 Subject: [PATCH] ci: Restart docker before starting There are many mysterious docker problems recently, one guess is that they might be caused by #1388 updating the buildkite stack. One idea we had was to restart docker daemon before each buildkite job. Some examples: https://buildkite.com/materialize/tests/builds/69819#018c1689-af50-429a-a915-4f08aa975c4e https://buildkite.com/materialize/tests/builds/69815#018c168c-8881-4238-912e-aa06d8b3c838 Hopefully fixes https://github.com/MaterializeInc/materialize/issues/23481 Depends on https://github.com/MaterializeInc/i2/pull/1408 --- ci/plugins/mzcompose/hooks/command | 1 + 1 file changed, 1 insertion(+) diff --git a/ci/plugins/mzcompose/hooks/command b/ci/plugins/mzcompose/hooks/command index a5ea7d8d138e9..e4c8232a031e1 100644 --- a/ci/plugins/mzcompose/hooks/command +++ b/ci/plugins/mzcompose/hooks/command @@ -31,6 +31,7 @@ date +"%Y-%m-%d %H:%M:%S" > step_start_timestamp # Docker Compose run, which can leave old containers or volumes around that will # interfere with this build. ci_collapsed_heading ":docker: Purging containers and volumes from previous builds" +sudo systemctl restart docker mzcompose --mz-quiet kill mzcompose --mz-quiet rm --force -v mzcompose --mz-quiet down --volumes