Skip to content
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

exec /docker-entrypoint.sh: exec format error. ARM Support? #488

Open
binuengoor opened this issue Feb 5, 2023 · 9 comments
Open

exec /docker-entrypoint.sh: exec format error. ARM Support? #488

binuengoor opened this issue Feb 5, 2023 · 9 comments
Labels
bug Something isn't working

Comments

@binuengoor
Copy link

Was trying to run the project on docker on an arm64 machine and ran into the following issue:

exec ./celery-slow-entrypoint.sh: exec format error
exec /usr/local/bin/api-entrypoint.sh: exec format error
exec ./celery-fast-entrypoint.sh: exec format error
exec /docker-entrypoint.sh: exec format error

Server Specs:

Server:
 Containers: 11
  Running: 4
  Paused: 0
  Stopped: 7
 Images: 9
 Server Version: 23.0.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 31aa4358a36870b21a992d3ad2bef29e1d693bec
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-1017-oracle
 Operating System: Ubuntu 22.04.1 LTS
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 23.43GiB
 Name: instance-20220906-1534
 ID: UPVQ:TUFK:N5GB:P3LP:EHZO:LQOW:EROY:PXM6:46MN:LL5S:FGSD:TVQW
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

I am very new to this. Is arm64 architecture not supported? Any possibility of adding support in the near future?

@JeffreyCA
Copy link
Owner

JeffreyCA commented Feb 6, 2023

Can you try building the images from source using up --build or build? The prebuilt images target amd64 I believe. I can look into how to support multiple architectures.

@binuengoor
Copy link
Author

binuengoor commented Feb 6, 2023

I ran the following and it did not make any difference. When I checked the images in portainer, it said amd64. So maybe its not building to the correct architecture with the following code and directly pulling from docker-hub? Am I doing this correctly? Thanks for your help.

docker-compose -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml up --build

image

@JeffreyCA
Copy link
Owner

Does this work?

docker-compose -f docker-compose.yml -f docker-compose.prod.yml -f docker-compose.prod.selfhost.yml -f docker-compose.build.yml build

I think it might fail because certain dependencies used like nnabla 1.26.0 do not support ARM64. Looks like newer versions support it but only on Python 3.9+ (the prebuilt images use Python 3.8).

@JeffreyCA JeffreyCA assigned JeffreyCA and unassigned JeffreyCA Feb 7, 2023
@JeffreyCA JeffreyCA added the bug Something isn't working label Feb 7, 2023
@binuengoor
Copy link
Author

That is correct.

Errored out
=> ERROR [jeffreyca/spleeter-web-backend:latest 6/9] RUN pip install --upgrade pip wheel && pip install -r requirements.txt

#0 10.75 ERROR: Could not find a version that satisfies the requirement nnabla==1.26.0 (from versions: none)
#0 10.75 ERROR: No matching distribution found for nnabla==1.26.0

What to do now?

@JeffreyCA
Copy link
Owner

Unfortunately there isn't a workaround at the moment

@binuengoor
Copy link
Author

Unfortunately there isn't a workaround at the moment

Well, thanks for looking into it. Hope some day it will be possible to have ARM support too. I will keep my eyes peeled. Thanks for your amazing work.

@binuengoor
Copy link
Author

@JeffreyCA any updates to this issue? Was the image versions updated to add arm support?

@JeffreyCA
Copy link
Owner

@binuengoor Sorry for the long turnaround, I didn't have a ARM device to easily test things. I just merged some fixes to support ARM in #930. Can you try the latest changes?

@microtherion
Copy link
Contributor

FWIW, I'm running on an arm64 machine, and it works well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants