Open FusselTV opened 1 year ago
This is an unraid specific problem. This OS has nonstandard docker setup.
I have adapted the image to run in read-only mode. Update your images and checks if it is fixed for you now.
I'm running into this same issue using container docker 982c027553d8
I have adapted the image to run in read-only mode. Update your images and checks if it is fixed for you now.
After updating the container, it no longer crashes and works for streaming. However, I still encounter permission errors during startup, and the entire log is filled with "ServiceBrowserThread-24|zc|run: got socket error." This might be on me because I route all traffic through GlutenVPN, and the container only has access to port 6878. I'm unsure if there are more ports that need to be opened to prevent this error.
First I can't reproduce your problems as I have no flash stick with GUID to run unraid. I hate such type of OSes
Second, I am not sure which service You are running: either acestream-engine or acestream-service. Please clarify this issue as these cases have different setups
Third, there is more suspicious error for me i.e. "cannot create directory"
Fourth, You shouldn't stick with 6878 port as it is internally used in the container only. Outside of container you can use any available ports, e.g. --publish 7868:6878
Fifth to exclude any incoming impacts follows these steps to ensure clean setup:
This will download latest image
It is acestream-engine and it should be publishing to 8008 which is open. im on the last docker image that was published 3 days ago.
fair on the pain points, ill try to compile a docker image locally and troubleshoot a bit more.
The "cannot create directory'' error indicates there are something wrong with your setup. You don't need to build the image locally it's enough to follow four steps above.
The issue is still present. To workaround it, just chmod 777 the /mnt/cache/appdata/acestream directory or whatever it has been set as acestream cache directory.
@cyruz-git, cache and other writable data are placed in memory
@vstavrinov
No idea what the Unraid docker maintainer did and I didn't investigate, but the workaround was a no-brainer considering the permission issue, it actually works...
@cyruz-git, The directory You mentioned or similar doesn't exists
@vstavrinov
Like you said here:
This is an unraid specific problem. This OS has nonstandard docker setup.
@cyruz-git
please, post here the container log
@vstavrinov it's the exact same log of @FusselTV.
The issue is the [Errno 13]. It seems that the /dev/shm/.ACEStream directory is owned by 99:users, so the ace user can't write in it, if not chmodded to 777.
@cyruz-git, try this:
docker run --name acestream-engine --detach --user root --env HOME=/srv/ace --publish 6878:6878 vstavrinov/acestream-engine ./start-engine --client-console --live-cache-type memory --state-dir /dev/shm/.ACEStream
Hello, I would like to say that the docker in Unraid has always worked perfectly for me. For a couple of months now in Spain the operators have been cutting off the acestream......for this we must install the latest acestream version so that it does not cut off after 15 minutes. Would you be so kind as to update the Unraid docker with the latest version of acestream? Every 15 minutes it cuts me off and I have to restart docker. Thank you very much and sorry for the English, I used Google translator.
@dandoweltas there is no new version available. The current image is already at the last version. See
https://docs.acestream.net/products/
The actual version is 3.1.75rc4_ubuntu_18.04_x86_64_py3.8
. You can see it in Dockrefile. Besides, I don't understand how any new version could help when internet provider ban the service.
@vstavrinov
Thank you very much for answering. I'll try installing the one you told me about in Unraid.
I was referring to this problem that existed with version 3.1.74, you had to use VPN.
Since they updated the versions there is no longer that cutoff at 15 minutes nor is it necessary to use a VPN.
3.1.80 and above are fine.
https://forum.acestream.media/t/acestream-disconnects-every-12-15-minutes/3766
Thank you very much for everything and sorry for the inconvenience.
Hi, While attempting to run this container on Unraid, I encountered this error. Do you have any thoughts on how to fix it?