Make WordPress Core


Ignore:
Timestamp:
03/21/2024 06:40:34 PM (2 years ago)
Author:
desrosj
Message:

Build/Test Tools: Fix bug pulling local environment containers on Apple silicone.

The MySQL Docker containers for versions 5.7 and below do not support recent Apple silicone chips. Previously this was fixed by including amd64/ as a prefix to the image name in the docker-compose.yml file (see [54096]). However, this stopped working after recent updates to Docker Desktop.

This changeset removes the amd64/ prefix for the image used as the database container and raises the default version of MySQL in the local development environment to the current LTS version (8.0). Because this version is still maintained, there are arm64 containers available to use.

This also documents a new workaround for contributors looking to run the local Docker environment using MySQL 5.7 or earlier, which entails creating a small docker-compose.override.yml.

Merges [57568] to the 6.4 branch.

Props bernhard-reiter, johnbillion, afragen, huzaifaalmesbah.
Fixes #59930.

Location:
branches/6.4
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/6.4

  • branches/6.4/README.md

    r57214 r57862  
    112112```
    113113
     114#### Resetting the development environment
     115
     116The development environment can be reset. This will destroy the database and attempt to remove the pulled Docker images.
     117
     118```
     119npm run env:reset
     120```
     121
     122### Apple Silicone machines and old MySQL versions
     123
     124The MySQL Docker images do not support Apple Silicone processors (M1, M2, etc.) for MySQL versions 5.7 and earlier.
     125
     126When using MySQL <= 5.7 on an Apple Silicone machine, you must create a `docker-compose.override.yml` file with the following contents:
     127
     128```
     129services:
     130
     131  mysql:
     132    platform: linux/amd64
     133```
     134
     135Additionally, the "Use Rosetta for x86/AMD64 emulation on Apple Silicon" setting in Docker needs to be disabled for this workaround.
     136
    114137## Credentials
    115138
Note: See TracChangeset for help on using the changeset viewer.