-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
mumble docker image error #39
Comments
How exactly do you run the image? |
Hi, I'm also having this issue. The Docker container fails to start with the same error: This is my version: "3.3"
services:
mumble-server:
container_name: mumble-server
ports:
- 64738:64738/tcp
- 64738:64738/udp
- 6502:6502/tcp
volumes:
- ./data/mumble:/data
restart: on-failure
image: mumblevoip/mumble-server:latest
environment:
- ice="tcp -h 127.0.0.1 -p 6502"
- icesecretwrite=**********
- allowping=true
- users=1000
- rememberchannel=true
- opusthreshold=0
- registerName=**********
- registerHostname=**********
networks: {} some information censored for privacy reasons System Information: I found this issue online, I don't know if that's relevant to this issue though: docker/compose#10185 |
Does it work without compose (Aka: a plain
How does this work? We don't have an image for this architecture yet 👀 |
Oh, I tried to run
Seems like arm64 / aarch64 isn't supported yet. Why? There are official Mumble server packages in the default repos for arm64. |
See #3 |
@sbodese any chance you are also using the docker image on a non-supported platform? |
Hi, thanks, jep i use armv71. |
Alright then I think we found the issue. It's weird that docker compose doesn't warn/error due to incompatible architecture though. |
Description
hi folks
the latest docker image
mumblevoip/mumble-server:latest
wont work
docker log says:
exec /entrypoint.sh: exec format error
Steps to reproduce
run the current docker image
Mumble version
mumblevoip/mumble-server:latest
Mumble component
Server
OS
Linux
Reproducible?
Yes
Additional information
No response
Relevant log output
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: