From fca182877ca616257527f6186dd1e88b2919feeb Mon Sep 17 00:00:00 2001 From: Justin Date: Thu, 10 Aug 2023 18:37:18 -0400 Subject: [PATCH] fix: Restart buildkit after containerd when provisioning (#461) Issue #, if available: Fixes #412 *Description of changes:* - Previously, only containerd was restarted after configuring it to use the data on the persistent disk. This changes the UUID of the server worker. BuildKit also needs to be restarted to use the proper UUID. See issue for why this is important. *Testing done:* - Local testing - [x] I've reviewed the guidance in CONTRIBUTING.md #### License Acceptance By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Signed-off-by: Justin Alvarez --- finch.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/finch.yaml b/finch.yaml index f1dcc0f43..745caf4b9 100644 --- a/finch.yaml +++ b/finch.yaml @@ -176,7 +176,9 @@ provision: mkdir -p ~/.local/share/cni sudo mount --bind /mnt/lima-finch/cni ~/.local/share/cni - sudo systemctl restart containerd.service + # Make sure buildkit is restarted with containerd, so it uses the correct UUID + sudo systemctl add-requires buildkit.service containerd.service + sudo systemctl restart containerd.service # Probe scripts to check readiness. # 🟢 Builtin default: null