magento / magento/magento-cloud-docker

No ARM images available for development on Macbook Pro M1 CPU

Open
#326 35 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted feature request help wanted Priority: P1 Progress: ready for grooming
Dominant language
PHP
Stars
277
Forks
187
PR merge metrics
No merged PRs in 30d

Description

### Preconditions
1. Macbook Pro M1 cpu
2. php 7.3
3. redis 5
4. elasticsearch 7.5 (attempted)
5. varnish (attempted)

### Steps to reproduce
1. ./vendor/bin/ece-docker build:compose
2. docker-compose up -d
3. multiple issues arise

### Expected result
1. docker containers should be created, and all start with no errors

### Actual result
1. elasticsearch issue
1. `Error: could not find libjava.so Error: Could not find Java SE Runtime Environment`
2. No ARM elasticsearch image provided by magento here: https://registry.hub.docker.com/r/magento/magento-cloud-docker-elasticsearch
3. workaround, to use elasticsearch own here, https://registry.hub.docker.com/_/elasticsearch?tab=tags&page=1&ordering=last_updated
1. e.g `image: 'elasticsearch:7.8.1'`
2. varnish issue
1. `varnish_1 | Error:
varnish_1 | Running VCC-compiler failed, signal 5
varnish_1 | VCL compilation failed`
2. There are no ARM varnish images available in magento or varnishes own docker repos

Is there a known way of getting cloud docker to boot on a new Macbook Pro?

Or is there a way to disable varnish, and have the docker just go straight to the frontend node to serve the site without a FPC?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing ./vendor/bin/ece-docker build:compose followed by docker-compose up -d on an M1 MacBook Pro, then inspect the generated service images and the Elasticsearch and Varnish startup errors. Done means the development containers start without errors, or the supported workaround and any way to disable Varnish are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, elasticsearch, php
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.