Skip to content

Commit

Permalink
chore(e2e/vmcompose): run docker compose down during ugprade (#1824)
Browse files Browse the repository at this point in the history
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
  • Loading branch information
corverroos authored Sep 5, 2024
1 parent 9b16965 commit 86b44e8
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions e2e/vmcompose/provider.go
Original file line number Diff line number Diff line change
Expand Up @@ -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)

Expand Down

0 comments on commit 86b44e8

Please sign in to comment.