[wp-trac] [WordPress Trac] #60901: GitHub Actions: Migrate to Docker Compose v2

[WordPress Trac]

#60901: GitHub Actions: Migrate to Docker Compose v2
-----------------------------------+-------------------------
 Reporter:  swissspidy             |       Owner:  swissspidy
     Type:  defect (bug)           |      Status:  reopened
 Priority:  high                   |   Milestone:  6.5.3
Component:  Build/Test Tools       |     Version:
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch fixed-major  |     Focuses:
-----------------------------------+-------------------------

Comment (by desrosj):

 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`, [https://github.com/docker/scan-cli-plugin 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.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60901#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform