This repository has been archived by the owner on Jul 22, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
overnode launch
fails on non-amd64 platform
#69
Comments
@jtagcat do you think it is reasonable to switch to linuxserver/docker-compose? I understand it is not official by docker... |
I'd say yes. Linuxserver is quite reputable. The official and linuxserver image may have differences — the change would need to be tested. |
Will docker pull automatically detect which architecture container to download? |
I think so, but it needs to be tested. I don't have an arm device, that I can run docker on in my current location (besides a raspi 1b). |
@Miroka96 then I believe you better propose pull request and test it for us. I do not have time capacity available to address this. Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
I came across this issue while trying to run overnode on an Odroid N2+, which has an arm64 (armv8) architecture. When running
overnode launch
, the docker-compose command fails, because it cannot find a platform-matching docker-compose image. Until docker/compose#6831 gets resolved on the docker-compose site, there are only amd64 docker-compose images.Wanted solution:
Until docker-compose fixes its issue, I would prefer switching to the
linuxserver/docker-compose
image, because it is multi-arch enabled. However, the tag naming scheme is slightly different.Currently, I am trying to build the docker-compose image myself to check whether the latest docker-compose Dockerfile produces at least a working armv8 image.
Best regards,
Miroka
The text was updated successfully, but these errors were encountered: