Multi Arch (ARM) Docker Support
Build the hypernode-docker images for multiple CPU architectures cfr: https://docs.docker.com/desktop/multi-arch/ in order to support Apple Silicon (ARM64).
The current x86_64 images are unusable on Apple Silicon computers; the nginx, mailhog and elasticsearch services crash either at launch or right after.
An extra benefit of having multi arch builds would that it probably opens up the possibility to also offer hosting on Amazon AWS Graviton.
Extra info:
Used software and Hardware:
- Macbook Pro (14-inch 2021)
- Chip: Apple M1 Max
- OSx: 12.0.1 (With Rosetta installed)
- Docker Desktop for Mac: 4.2.0 (70708)
- Docker Engine: 20.10.10
-
Thorvald Verlaeckt commented
Any updates on this? This is becoming a blocking issue.
-
Jens Bourgeois commented
Hi guys,
We are really facing problems without the ARM support.
Our last few new colleagues are using M1 chips and can not complete the documentation for setting up new projects. It's only a matter of time before devs on Apple machines will all use the M1 chip over the Intel chip, could this be reconsidered?Thanks in advance
-
Arthur Venis commented
We are facing the same issue. We have a collection of 6 Apple machines, of which the latest iMac features the new M1 chip. We use Docker heavily in local Magento 2 development.
The new Mac is unusable as we got it to build, but you can't do anything. You can remove lua refs, don't use Varnish, but without ElasticSearch; you can't run Magento. So with that: end of the story.
We are now looking at moving to PHPStorm Remote Development using the JetBrains Gateway running on a development hypernode. The setup works more or less ok, as you no longer use the local machine. Still, it requires a heavier development hypernode, and it is questionable whether it can support multiple sessions.
And, apart from this, you need xdebug on the hypernode, which is not standard. Byte has it installed for me, but it's not working (yet) due to port conflicts on port 9000.
So yes, an ARM64 build is very much appreciated.
-
Hi Tjerk,
We reviewed this issue and unfortunately we're not going to follow up on this one (yet).
If substantially more use cases show up in the future, we will definitely reconsider picking this up in the future. -
Tjerk Ameel commented
Hey guys,
How's the reviewing going?