[wp-trac] [WordPress Trac] #52591: Update mysql image in WordPress Docker setup to work on arm architectures
WordPress Trac
noreply at wordpress.org
Mon Feb 22 13:22:58 UTC 2021
#52591: Update mysql image in WordPress Docker setup to work on arm architectures
------------------------------+------------------------------
Reporter: justinahinon | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version:
Severity: normal | Resolution:
Keywords: has-patch close | Focuses:
------------------------------+------------------------------
Changes (by desrosj):
* keywords: has-patch => has-patch close
* version: trunk =>
Comment:
I was working through this with @afragen over the weekend as well. It's
likely that this will be fixed upstream, so I'm hesitant to make this
temporary change.
For the time being, you can easily work around this with two approaches.
1. Create a `docker-compose-override.yml` file and define the `mysql`
container with the `platform` specified.
2. Use `mariadb` instead of `mysql`. You can do this by changing the
`.env` file `LOCAL_DB_TYPE` and `` variables locally to `mariadb` and
`latest` or by exporting those variables using command line before running
`npm run env:start`.
I am writing a Build/Test Tools post for the Make Core blog detailing
several tooling updates and I will include a small section detailing this
and other small M1 issues that have been discovered.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52591#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list