[wp-trac] [WordPress Trac] #57896: Improve devcontainer + Codespaces support

[WordPress Trac]

#57896: Improve devcontainer + Codespaces support
------------------------------+-----------------------------
 Reporter:  SergeyBiryukov    |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+-----------------------------

Comment (by mdawaffe):

 Replying to [comment:6 rmccue]:
 > I actually did manage to get it to work in the end... -ish. Rather than
 using core's containers for the "main" (`service`) container, I'm using a
 container built off `mcr.microsoft.com/devcontainers/base` with an
 extended docker-compose, which means we don't need to modify the main file
 (but can override it if needed).

 That's what I was going to try next. Thank you for beating me to it :)

 > The problem I ended up with though is that MySQL is not accepting
 connections for root from 172.18.0.0/16; the config ''should'' be allowing
 `%` for the host so not sure what's going on there.

 Pretty sure this is not a bind issue. I ran into this as well: The MySQL
 container is not running its initialization:
 * https://github.com/docker-
 library/mysql/blob/c13cda9c2c9d836af9b3331e8681f8cc8e0a7803/5.7/docker-
 entrypoint.sh#L302-L305
 * https://github.com/docker-
 library/mysql/blob/c13cda9c2c9d836af9b3331e8681f8cc8e0a7803/5.7/docker-
 entrypoint.sh#L416

 (You can tell since the user.myd file is 0 bytes.)

 It magically fixed itself when I committed my changes to my own fork
 rather than having uncommitted changes in yours. (Correlated not causal, I
 suspect.)

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