[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):

 > I think the behaviour you were seeing with docker-compose cli ...
 working was because it was starting a new CLI service.

 Agreed. I don't remember the details or what all I tried, but I think the
 issue was that the initial containers were created in one configuration
 with respect to the devcontainer container (as children? as siblings?) and
 the newly created CLI container was created with another.

 > I also tried switching over to use the main docker-compose we already
 have, but that causes errors for some reason - it's very hard to see in
 the build logs exactly why that happens.

 As best I can tell, `docker-outside-of-docker` isn't working with core's
 docker-compose.yml because of `nginx:alpine`, which doesn't have `apt-get`
 (see
 [https://github.com/devcontainers/features/blob/038bed3d58a84885da8a008b80905da17d57a543/src
 /docker-outside-of-docker/install.sh#L70 docker-outside-of-docker's
 install.sh], [https://github.com/devcontainers/features/tree/main/src
 /docker-outside-of-docker#os-support OS Support]). Alpine uses
 [https://docs.alpinelinux.org/user-handbook/0.1a/Working/apk.html apk].
 Switching to `nginx:latest` fixes that problem, though others crop up.

 I'll drop a link on your PR to some changes that mostly work.

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