Use docker-compose 2.7.0 instead of 2.2.3 in CI

[aminvakil]

Then I'm going to implement #1294 (comment), but first this needs to be merged.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[ethanhs]

Thank you for this!

[ethanhs]

Closing/reopening because the integration tests seemed stalled.

[aminvakil]

Closing/reopening because the integration tests seemed stalled.

I think the stalled test is because it has been changed, and is a github bug.

We don't need to run our test on 2.2.3 .

[aminvakil]

https://github.com/docker/compose/releases/tag/v2.8.0 has been released, do we want to bump to 2.8.0 instead of 2.7.0?

[ethanhs]

https://github.com/docker/compose/releases/tag/v2.8.0 has been released, do we want to bump to 2.8.0 instead of 2.7.0?

I think that is fine! The goal is to use a newer compose, right?

[aminvakil]

https://github.com/docker/compose/releases/tag/v2.9.0 has just been released :)

[BYK]

Maybe we should schedule a daily cron job to update the version :P

[ethanhs]

Alright hopefully they don't release another before CI finishes, but once CI is finished I will merge this :)

Should we remove the integration test that we seem not use anymore?

[aminvakil]

  Notice: 01 17:05:36 [notice] 24#24: signal process started
  docker: Error response from daemon: network self-hosted-1_default not found.
  An error occurred, caught SIGERR on line 9
  *NOT* cleaning up, to clean your environment run "docker compose stop".

Seems like we're facing new problems 😢
Closing and reopening to trigger CI.

[aminvakil]

Alright hopefully they don't release another before CI finishes, but once CI is finished I will merge this :)

Should we remove the integration test that we seem not use anymore?

I think it will be removed once this is merged, we will see on #1600 then.

[aminvakil]

Yes, we're facing new problems 😭

  Notice: 02 09:23:18 [notice] 24#24: signal process started
  docker: Error response from daemon: network self-hosted-1_default not found.
  time="2022-08-02T09:23:18Z" level=error msg="error waiting for container: context canceled"
  An error occurred, caught SIGERR on line 9
  *NOT* cleaning up, to clean your environment run "docker compose stop".

Trying docker-compose 2.8.0 now.

[aminvakil]

  Error response from daemon: Conflict. The container name "/sentry-self-hosted-snuba-cleanup-1" is already in use by container "6fd4b47b6c33bb1cb997b6bdb8041a7f052f5e329fa27d907066333a987a8389". You have to remove (or rename) that container to be able to reuse that name.

[aminvakil]

  Notice: 02 10:11:40 [notice] 24#24: signal process started
  docker: Error response from daemon: network self-hosted-1_default not found.
  time="2022-08-02T10:11:40Z" level=error msg="error waiting for container: context canceled"
  An error occurred, caught SIGERR on line 9
  *NOT* cleaning up, to clean your environment run "docker compose stop".
  Error: Process completed with exit code 125.

on docker-compose 2.8.0 too.

I've seen something like this on our instance too one time with docker-compose 2.8.0 .

From https://github.com/docker/compose/releases/tag/v2.8.0:

This release introduced a breaking change via compose-go v1.3.0 and this compose-spec/compose-go#294.
Docker Compose will recreate new resources (networks, volumes, secrets, configs...) with new names, using a - instead a _ and try to connect/use to this new created resources instead of your existing ones!
Please use Compose v2.9.0 instead

But still it seems like both 2.8.0 and 2.9.0 got problems.

[ethanhs]

Thanks for changing this!