From 86b44e8f7bc82292773e320bedc687ea59129287 Mon Sep 17 00:00:00 2001 From: corver Date: Thu, 5 Sep 2024 17:10:59 +0200 Subject: [PATCH] chore(e2e/vmcompose): run docker compose down during ugprade (#1824) Only running `docker compose up -d` doesn't always result in all changes reflecting in services since docker only restarts the container if the docker-compose file itself changed. If only artefacts changed, the container isn't restarted. This ensures that we always restart the containers. issue: none --- e2e/vmcompose/provider.go | 1 + 1 file changed, 1 insertion(+) diff --git a/e2e/vmcompose/provider.go b/e2e/vmcompose/provider.go index 9f0832d43..00a0adc85 100644 --- a/e2e/vmcompose/provider.go +++ b/e2e/vmcompose/provider.go @@ -278,6 +278,7 @@ func (p *Provider) Upgrade(ctx context.Context, cfg types.ServiceConfig) error { startCmd := fmt.Sprintf("cd /omni/%s && "+ "sudo mv %s docker-compose.yaml && "+ + "sudo docker compose down && "+ "sudo docker compose up -d", p.Testnet.Name, composeFile)