[flake] Docker restart fails in BMO e2e

[tuminoid]

Which jobs are flaking?

BMO e2e tests

Which tests are flaking?

Randomly any of e2e variants

Since when has it been flaking?

Since moving to GH actions.

Jenkins link

https://github.com/metal3-io/baremetal-operator/actions/runs/9477201984/job/26111334840

Reason for failure (if possible)

n 12 05:29:25 minikube systemd[1]: docker.service: Deactivated successfully.
Jun 12 05:29:25 minikube systemd[1]: Stopped Docker Application Container Engine.
Jun 12 05:29:25 minikube systemd[1]: Starting Docker Application Container Engine...
Jun 12 05:29:25 minikube dockerd[796]: time="2024-06-12T05:29:25.668001724Z" level=info msg="Starting up"
Jun 12 05:30:25 minikube dockerd[796]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceeded
Jun 12 05:30:25 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 05:30:25 minikube systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 12 05:30:25 minikube systemd[1]: Failed to start Docker Application Container Engine.

Anything else we need to know?

No response

Label(s) to be applied

/kind flake

[Rozzii]

/triage accepted

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[tuminoid]

/remove-lifecycle stale
/lifecycle frozen

This is very much still happening.

[tuminoid]

We run 6 tests nightly, and every day 1 or 2 have failed to this issue. Some PR jobs also randomly fail to this.

We should try to find a workaround at least, if actual fix is not possible.

[lentzi90]

I have switched my playground to use kind. If I can manage to get a couple of hours for this, it should be possible to do the same for BMO e2e.

[tuminoid]

/assign @lentzi90