You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arrow's CI and documentation reference docker-compose in many places which is the old V1 way of calling into Docker Compose, see https://docs.docker.com/compose/migrate/ for more background on docker-compose vs docker compose. It should be safe to update all references to docker-compose to use the current docker compose.
Note: What prompted this issue is that CI just started failing due to the GitHub Actions runners not being able to find docker-compose. See 1, 2. This was caused by GHA runner image release 20240804 finally removing docker-compose.
There's already a minor PR updating CI and it would be good to follow up with a PR updating references everywhere else as I think (1) most developer systems should have V2 now and (2) V1 may slowly get phased out of package managers.
Component(s)
Continuous Integration, Developer Tools
The text was updated successfully, but these errors were encountered:
…"docker compose" (#43575)
### Rationale for this change
This is a follow-on to #43566 which was merged earlier today. See #43570 for more detail on the entire set of changes.
### What changes are included in this PR?
- Replace instances where we call or document calling `docker-compose` with `docker compose`.
### Are these changes tested?
Yes.
### Are there any user-facing changes?
This PR includes the require user-facing changes to document things.
* GitHub Issue: #43570
Lead-authored-by: Bryce Mecum <petridish@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Describe the enhancement requested
Arrow's CI and documentation reference
docker-compose
in many places which is the old V1 way of calling into Docker Compose, see https://docs.docker.com/compose/migrate/ for more background ondocker-compose
vsdocker compose
. It should be safe to update all references todocker-compose
to use the currentdocker compose
.Note: What prompted this issue is that CI just started failing due to the GitHub Actions runners not being able to find
docker-compose
. See 1, 2. This was caused by GHA runner image release 20240804 finally removingdocker-compose
.There's already a minor PR updating CI and it would be good to follow up with a PR updating references everywhere else as I think (1) most developer systems should have V2 now and (2) V1 may slowly get phased out of package managers.
Component(s)
Continuous Integration, Developer Tools
The text was updated successfully, but these errors were encountered: