acelink: Unable to run Ace Link on Apple M1

Describe the bug

Unable to run Ace Link

What I expected to happen

Ace Link to run

Additional debug info

System info:

MacBook Pro M1 Docker installed VLC installed Ace Link installed (using Homebrew)

Here’s the out put of docker logs acelink--ace-stream-server

2021-06-01 20:05:53,586|MainThread|acestream|init segmenter failed
Traceback (most recent call last):
  File "core.c", line 333, in
ImportError: cannot import name pysegmenter
2021-06-01 20:05:53,588|MainThread|acestream|platform=linux
2021-06-01 20:05:53,591|MainThread|acestream|app=acestream
2021-06-01 20:05:53,591|MainThread|acestream|version=3.1.49 code=3014900 revision=365f84f date=2019-07-11
2021-06-01 20:05:53,591|MainThread|acestream|use_local_db=True
2021-06-01 20:05:53,592|MainThread|acestream|use_m2crypto=True
2021-06-01 20:05:53,592|MainThread|acestream|is_gui_mode=0
2021-06-01 20:05:53,593|MainThread|acestream|enable debug: 0
2021-06-01 20:05:53,604|MainThread|acestream|get_default_api_version: 2
2021-06-01 20:05:53,604|MainThread|acestream.coreapp|use fixed i2i_port: 62062
2021-06-01 20:05:53,605|MainThread|acestream.coreapp|state_dir=u'/root/.ACEStream'
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
/bin/ls: cannot access '/dev/disk/by-id/': No such file or directory
2021-06-01 20:05:54,545|MainThread|acestream.coreapp|set_debug_from_ui: level=0
2021-06-01 20:05:54,549|MainThread|acestream|enable debug: 0
2021-06-01 20:05:54,591|MainThread|acestream.coreapp|cannot load session config, use default
: error fetching interface information: Device not found
2021-06-01 20:05:54,761|MainThread|acestream.SocketHandler.InterruptSocket|bound on 127.0.0.1:51351
2021-06-01 20:05:54,762|MainThread|acestream.SocketHandler.SocketHandler|bind: socket bound: host=0.0.0.0 port=8621
2021-06-01 20:05:54,762|MainThread|acestream.LM|listen on 8621
2021-06-01 20:05:54,834|AceStreamCoreThread|acestream.SocketHandler.SocketHandler|create_multicast_sockets: failed to create socket: ip=239.255.17.18 port=32968 local=172.17.0.2
Traceback (most recent call last):
  File "ACEStream/Core/BitTornado/SocketHandler.py", line 842, in create_multicast_sockets
  File "ACEStream/Core/BitTornado/SocketHandler.py", line 860, in create_single_multicast_socket
  File "/usr/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 92] Protocol not available
2021-06-01 20:05:54,852|MainThread|acestream.VideoServer|start: addr= port=6878 allow_remote=1 allow_intranet=1
2021-06-01 20:05:55,712|MainThread|acestream.coreapp|failed to start aircast manager
Traceback (most recent call last):
  File "core.c", line 1483, in
  File "core.c", line 122, in
  File "core.c", line 290, in
  File "ACEStream/third_party/zeroconf/zeroconf.py", line 1400, in __init__
  File "ACEStream/third_party/zeroconf/zeroconf.py", line 1437, in _init_sockets
  File "/usr/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 92] Protocol not available
2021-06-01 20:05:55,722|ServiceTaskQueueThread-2|acestream.Session|sync_time: no response
2021-06-01 20:05:55,746|MainThread|acestream.SocketHandler.InterruptSocket|bound on 127.0.0.1:37736
2021-06-01 20:05:55,747|MainThread|acestream.SocketHandler.SocketHandler|bind: socket bound: host=0.0.0.0 port=62062
2021-06-01 20:05:55,749|Instance2InstanceThread-32|acestream.APIServer|run: ready to receive remote commands on 62062
Exception in thread ZeroconfThread-24:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "ACEStream/third_party/zeroconf/zeroconf.py", line 849, in run
  File "ACEStream/third_party/zeroconf/zeroconf.py", line 1452, in _periodic_check
AttributeError: 'Zeroconf' object has no attribute 'last_sockets_check'

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 16 (6 by maintainers)

Most upvoted comments

Yes I messed something up, I created an ARM version of the Docker image using the AMD64 binary of the Acestream server, which is not going to work because it’s the wrong arch.

There is an ARM version of the ace stream server for Android, ~there are existing Docker images based on this (eg https://github.com/lucabelluccini/acestream-engine-armv7-docker)~ M1 is ARMv8 so this won’t work, but I don’t have access to an M1 machine to convert this into a working solution for Ace Link.

I’m having the same problem. Version 1.9.0 installed, unchecked experimental features in docker

For M1 users: The AMD64 version works with Docker when you uncheck experimental features in Docker’s preferences, see https://github.com/blaise-io/acelink/issues/38