-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Everest Not running on Mac silicon **no matching manifest for linux/arm64/v8 in the manifest list entries** #48
Comments
I've included a new readme.md for EVerest in /server/EVerest/readme.md regarding running Everest with Mac arm64 settings: @thanaParis Please approve for merging, thank you💙. |
@hpxix we were looking deeper into this as well, and we did see that initially on ARM64 we see the
Were you able to get around this and actually have Everest running? |
I followed the changes that you have made in the video https://www.loom.com/share/e7fd054e4d224918a722d14eb834665b and I am seeing the above error ( I am on a 2021 Macbook Pro with Apple M1 Max Chip. I tried running via |
Actually, my PR didn't include all changes but if you go through my version of the fix for the issue above it'll work, Main changes that are done in docker-compose.yml; add platform tag = linux/amd64 to all services, remove in manager service; Instead added network tag to use bridge for all services For Dockerfile simply just change platform to linux/amd64 @elliot-sabitov let me know how this goes for you also use docker compose to run everest and not node or at least that what works for me @thanaParis Also I'll make sure to include the new updates on my PR Cheers💙 |
…r linux/arm64/v8 in the manifest list entries** citrineos#48 Issue: citrineos/citrineos#48
@thanaParis I've added a new PR with the latest changes on the readme.md for server/everest: |
@hpxix I tried with the following 2 files just now (see below) that I got from your commit here citrineos/citrineos-core@eceaaec, but unfortunately I am still seeing this error
and
|
@elliot-sabitov Here are things I'd consider if i was facing that problem,
If it wasn't running try pulling it using: also try running the image using: |
Hi @hpxix , when I run
When I run @hpxix Can you please try running I did upgrade my docker to the latest version 4.34.3 but I am still seeing the same behavior, as soon as the Everest manager container starts up, it exists, and checking the logs, I still see the following output:
|
To provide an update, I had another developer using Macbook Pro with M1 chip try the above, and she also experienced the same issue Thank you in advance for your patience. |
Which repository?
Is it:
Describe the bug
Description: Running the EVerest charger simulator on Mac Silicon (M1/M2) presents compatibility issues due to differences in architecture, as Docker defaults to pulling AMD64 images that are incompatible with ARM64 processors. This causes errors when attempting to start the containers in the /Server/everest directory using the docker-compose.yml setup.
ERROR
no matching manifest for linux/arm64/v8 in the manifest list entries
Proposed Solution:
To ensure compatibility and allow EVerest to run smoothly on Mac Silicon, we propose the following adjustments to the docker-compose.yml file:
Platform Specification:
Add platform: linux/amd64 under each service definition to enforce Docker’s usage of AMD64 images with ARM64 emulation on Apple Silicon.**
Direct Environment Variables:
For simpler configuration, define EVEREST_IMAGE_TAG and EVEREST_TARGET_URL directly in the environment section within docker-compose.yml. This avoids needing dynamic build-time arguments and simplifies setup.
Updated docker-compose.yml Example aka FIX:
Dockerfile:
Steps to Reproduce:
Clone the EVerest repository and navigate to /Server/everest.
Run npm run start-everest or npm run start-everest-windows to start the Docker containers.
Observe any errors related to architecture incompatibility.
Expected Outcome:
With the platform: linux/amd64 specification, Docker should emulate AMD64, allowing the containers to run seamlessly on Mac Silicon. Users should then be able to access the EVerest UI at [localhost|ip]:1880/ui/ and view OCPP logs at localhost:8888.
Additional Context:
This fix aims to support ARM64 users by simplifying the setup and ensuring all components are appropriately configured for cross-platform compatibility.
I'll commit a new Readme.md for EVerest for Mac Users later today have a great one!
The text was updated successfully, but these errors were encountered: