[wp-trac] [WordPress Trac] #64654: Docker images in wordpress-develop do not support on Apple Silicon

WordPress Trac noreply at wordpress.org
Fri Feb 20 10:01:52 UTC 2026


#64654: Docker images in wordpress-develop do not support on Apple Silicon
------------------------------+------------------------------
 Reporter:  huzaifaalmesbah   |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by mcsf):

 Replying to [comment:4 ellatrix]:
 > What worked for me is pulling the images manually (I already had "Use
 Rosetta for x86_64/amd64 emulation on Apple Silicon" on but that by itself
 didn't work).
 >
 > docker pull --platform linux/amd64 wordpressdevelop/php:latest
 > docker pull --platform linux/amd64 wordpressdevelop/cli:latest
 >
 > Then npm run env:start worked using that cache.

 This doesn't do anything for me, but I suppose it's unsurprising because
 it's pulling the same images that I was already using. The real issue is
 that there are no images for Apple Silicon, and so Docker tries to emulate
 amd64 and fails. Now as to why I experience this and you don't...? I
 really don't know. Subtle differences in the OS's emulation ability? I
 thought for a second it might because you're on macOS Tahoe and I'm
 holding on to Sequoia, but I see that the reports from huzaifaalmesbah and
 noruzzaman explicitly mention Tahoe, so ¯\_(ツ)_/¯.

 Btw, I should have shared earlier that I do think this comes down to
 emulation: the PHP container always fails when it tries to run its default
 command — [https://www.php.net/manual/en/install.fpm.php `php-fpm`] — and
 its only log message is:


 {{{
 $ docker-compose logs php
 php-1  | qemu-x86_64: QEMU internal SIGSEGV {code=MAPERR,
 addr=0xffff9cdc06c4}
 }}}

 Just to be safe, I tried (re)installing Rosetta, but the outcome's the
 same.

 Corroborating the idea that it's `php-fpm` specifically:


 {{{
 # I'm able to start an interactive throwaway container exec'ing bash:
 $ docker run -it --rm  wordpressdevelop/php:latest bash
 WARNING: The requested image's platform (linux/amd64) does not match the
 detected host platform (linux/arm64/v8) and no specific platform was
 requested
 root at 076162487f7f:/var/www#

 # php itself runs:
 root at 076162487f7f:/var/www# php -r 'echo 42, PHP_EOL;'
 42

 # but FPM (FastCGI Process Manager) doesn't:
 root at 076162487f7f:/var/www# php-fpm
 qemu-x86_64: QEMU internal SIGSEGV {code=MAPERR, addr=0xffffafa98c44}
 Segmentation fault
 }}}

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


More information about the wp-trac mailing list