#60901 closed defect (bug) (fixed)
GitHub Actions: Migrate to Docker Compose v2
Reported by: | swissspidy | Owned by: | swissspidy |
---|---|---|---|
Milestone: | 6.6 | Priority: | high |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch fixed-major |
Focuses: | Cc: |
Description
Right now a lot of our GitHub Actions workflows are failing.
The reason is that GitHub started removing Docker Compose v1 and the rollout is taking a few days.
Docker Compose v2 was released years ago and the migration should be pretty straightforward.
The main difference is that docker-compose
is no longer a valid command. You need to use docker compose
.
Change History (46)
This ticket was mentioned in PR #6349 on WordPress/wordpress-develop by @swissspidy.
10 months ago
#1
- Keywords has-patch added
@swissspidy commented on PR #6349:
10 months ago
#2
The current test failures all seem to be related to 502 Bad Gateway errors on WordPress.org.
@swissspidy commented on PR #6349:
10 months ago
#3
Some of the PHPUnit test failures are because the workflow uses the phpunit-tests-run.yml
file from trunk, which doesn't yet have this fix.
This will be resolved when committing this change to trunk.
Same with the performance tests failures, which check out the previous commit which of course still uses docker-compose
.
#4
@
10 months ago
- Milestone changed from Awaiting Review to 6.5.1
Moving to 6.5.1 as we probably need to backport this to all the older branches.
#5
@
10 months ago
- Owner set to swissspidy
- Resolution set to fixed
- Status changed from new to closed
In 57918:
@swissspidy commented on PR #6349:
10 months ago
#6
Committed in https://core.trac.wordpress.org/changeset/57918
There will likely be some follow-up commits though.
This ticket was mentioned in Slack in #core by jorbin. View the logs.
10 months ago
This ticket was mentioned in Slack in #core by jorbin. View the logs.
10 months ago
This ticket was mentioned in Slack in #core by jorbin. View the logs.
10 months ago
#17
@
9 months ago
This is blocked by #60822.
I'm also seeing some warnings locally. I don't think that they're related to [57918], though. I just wanted to mention them here in case anyone else noticed these.
WARNING: Plugin "/Users/username/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/username/.docker/cli-plugins/docker-scan: no such file or directory WARNING: daemon is not using the default seccomp profile WARN[0000] /Users/username/Sites/wordpress-svn/six-two/docker-compose.yml: `version` is obsolete
For docker scan
, this was archived in favor of docker scout
. I fixed this by navigating to the ~/.docker/cli-plugins
folder and manually deleting the docker-scan
alias. The source file had been properly deleted, but for some reason the alias remained and Docker was trying to use it.
I haven't figured out how to fix the seccomp
warning. And I opened #61101 for the fourth one.
I think we could probably backport this, #60822, and #61101 at the same time.
Trac ticket: https://core.trac.wordpress.org/ticket/60901