[wp-trac] [WordPress Trac] #59930: Problems pulling relevant MySQL Docker container

[WordPress Trac]

#59930: Problems pulling relevant MySQL Docker container
------------------------------+---------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  6.5
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+---------------------

Comment (by Bernhard Reiter):

 Replying to [comment:7 desrosj]:
 > @bernhard-reiter does [attachment:"59930.diff"] also work for you?

 It does, yes!

 > I would be in favor of bumping the default version of MySQL to 8.0,
 which is the latest LTS version. 8.1 and 8.2 support is more complicated.
 Even though they are production-grade releases, they are "innovation
 releases" that are only supported for roughly 1 quarter (~4 months). It's
 still not clear how or if we should support them (see #59779 for more
 details there).

 Right, makes sense. I wasn't aware of their LTS/"innovation" release
 split, but LTS makes more sense, of course.

 > [attachment:"bump-mysql-to-8-2.diff"] seems good at the surface, but
 doesn't solve the problem. When someone with `arm64` changes the version
 of MySQL being used to 5.7 without knowledge of this issue or a way around
 it, then their environment would show the problem and back to square one.
 It would be great if there were conditional statements supported within
 Docker configuration files, but they only support
 [https://docs.docker.com/compose/compose-file/compose-file-v3/#variable-
 substitution variable substitution]. So in order to dynamically configure
 the right platform (if running `arm64` & DB type is MySQL & version <=
 5.7, use `linux/amd64` instead).

 Heh, I went through a similar thought process (also tried looking for a
 conditional syntax in the Docker compose file).

 Ultimately, I thought it might be permissible to set a default like this,
 even if that means that users will have to exert more caution when trying
 to use a different version (for which no `arm64` image exists, in this
 case); the error message might provide enough of a pointer in the right
 direction. But yeah, not sure it's worth confusing some users, unless we
 see e.g. huge performance benefits from using `arm64` images on Apple
 Silicone.

 Anyway, I'm fine with proceeding with your patch for now -- bumping the
 MySQL version is something we can consider doing later.

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