v2.0.3 down't not start docker container

Question

v2.0.3 down't not start docker container

AndrewP-GH opened this issue a year ago · comments

Describe the bug
After updating from 2.0.2 to 2.0.3 ace-link doesn't work anymore. I see that the docker container doesn't start.
My PC: macos ventura 13.2.1 — m1 pro
Docker version 20.10.24
Docker Desktop v4.18.0

nebelnic · Answer 1 · Sat Apr 15 2023 01:02:12 GMT+0800 (China Standard Time)

Same here with Ventura 13.3 m2

Blaise Kal · Answer 2 · Sat Apr 15 2023 03:17:41 GMT+0800 (China Standard Time)

I will debug next week when I have access to an M1 machine.

In the meantime 2.0.2 still works?

Andrew Paramonov · Answer 3 · Sat Apr 15 2023 05:16:37 GMT+0800 (China Standard Time)

yes, 2.0.2 works as expected in this case)

Andrew Paramonov · Answer 4 · Sat Apr 15 2023 05:36:52 GMT+0800 (China Standard Time)

@blaise-io I've debugged the app and found out that the problem is:
Error: No such image: blaiseio/acelink:2.0.3

Andrew Paramonov · Answer 5 · Sat Apr 15 2023 05:42:42 GMT+0800 (China Standard Time)

So, to solve this issue we have to add --platform=linux/amd64 to docker pull command for Apple CPU

Andrew Paramonov · Answer 6 · Sat Apr 15 2023 05:57:09 GMT+0800 (China Standard Time)

I have made the PR to solve this issue. The problem is not in the latest release, this bug has already been with us for a long time :)

Blaise Kal · Answer 7 · Sat Apr 15 2023 15:11:20 GMT+0800 (China Standard Time)

Thanks again @AndrewP-GH. I also tagged 2.0.2 as 2.0.3 for the time being, so a local docker pull docker.io/blaiseio/acelink:2.0.3 should also fix the issue. I will now publish a 2.0.4 of shame.