https://www.spryker.com logo
Join Slack
Powered by
Hi all, after update our docker-sdk to latest rel...
# docker
m
Hi all, after update our docker-sdk to latest release (1.46.0 - Docker Compose V2) and merged the master in our 
apple-m1
branch (respectively apple-m1-adjustment) we got the follow error on sdk up 
Error response from daemon: image with reference spryker/chromedriver was found but does not match the specified platform: wanted linux/arm64/v8, actual: linux/amd64
If I turn off the chromedriver then i got: 
Error response from daemon: image with reference wernight/phantomjs:latest was found but does not match the specified platform: wanted linux/arm64/v8, actual: linux/amd64
Anyone in the same situation? Thanks in advance!
If I don't want any webdriver then it is not possible at the moment
Copy code
// TODO Make it optional in next major
// Making webdriver as required service for BC reasons
if (empty($projectData['services']['webdriver'])) {
    $projectData['services']['webdriver'] = [
        'engine' => 'phantomjs',
    ];
}
v
m
nö... the spryker/chromedriver latest now support also the linux/arm64, therefore I think it is not more necessary 
{{ project._platformCompose }}
in 
generator/src/templates/service/chromedriver/default/chromedriver.yml.twig
But after this i got
Copy code
Error response from daemon: image with reference swaggerapi/swagger-ui:v3.24.3 was found but does not match the specified platform: wanted linux/arm64/v8, actual: linux/amd64
I think that the problem is strict related to Docker Compose V2 and the Experimental Apple-M1-Adjustment Branch... With docker compose V1 it worked very well for ca. 2 months now...
@high-pencil-62400 any quick feedback maybe from u? thanks
p
I pinged it internally that somebody with m1 please have a look
m
thank Florian 🙂 maybe a merge master -> apple-m1-adjustment it will be also cool to have... then is 
apple-m1-adjustment
synced too..
the same happened for redis-commander
Copy code
Error response from daemon: image with reference rediscommander/redis-commander:latest was found but does not match the specified platform: wanted linux/arm64/v8, actual: linux/amd64
o
Hey @mammoth-autumn-37948, Introduced Docker Compose V2 support doesn't affect ChromeDriver. Can you please execute: 
docker pull spryker/chromedriver && docker/sdk boot {deploy file} && docker/sdk up
. Unfortunately, you cannot use 
wernight/phantomjs
and 
swaggerapi/swagger-ui
as they don't support ARM architecture.
m
@orange-book-10869 I have docker/sdk on M1 running since ca. 2 months and with swagger-ui too... Chromedriver u are right.. is compatible with ARM64 and I don't know why after enabling Docker Compose V2 has generated the error..
the same for 
rediscommander/redis-commander
always running and now not more after DC V2
I will try again with V1 and give u a feedback...
👍 1
• Docker Compose V2 disabled. • Mutagen resetted to mutagen-beta As before it run everything on Mac M1 Actual Branch is Master (Tag 1.45.7) merged in our local apple-m1-adjustment branch
die container (image) running now on my M1 with docker compose v1, sdk version 1.45.7 in apple-m1-adjustment branch
h
Hello Giovanni, What is the status of the issue right now?
m
That with Docker Compose V2 (latest Release 1.46.0) there are some problems with M1.. We have a local branch apple-m1 (just the apple-m1-adjustment original branch) but than spryker we merge master oft into it to allow the same features for M1 and not M1 developers. Today after merge the master (1.46.0) in our apple-m1 branch i got the errors above reported... With Docker Compose V1 it runs everything on M1 (redis-commander, swagger-ui tooo).. With Docker Compose V2 the container come not more up (missing arch image).
👍 1
o
JFYI; @nice-refrigerator-52084 M1 + Docker Compose V2
✅ 1
m
@orange-book-10869 any news? Did u tested it too or not yet?
o
@mammoth-autumn-37948,not yet but we added this case as we are on the testing stage of an official docker/sdk support for M1 arch.
👍 1
m
@orange-book-10869 any news?
what is about official M1 support too? It was promised at end Q1.. 🥸
o
Hi @mammoth-autumn-37948, the current status - In QA. Yes, you are absolutely right, it was planned for the end of Q1 but unfortunately it has been delayed due to several critical issues.
👌 1
p
btw, m1 support for most services is now included in the docker-sdk master 🙂 Please also have a look here: https://docs.spryker.com/docs/scos/dev/technical-enhancement-integration-guides/switch-to-arm-architecture-m1-chip.html
👍 2
2 Views
Open in Slack
PreviousNext
Powered by