Unraid install: binaries not executable

[TheRealZGYT]

Trying to get this to run on Unraid, managed to add the container but this is the error I'm getting when it starts.

This is the log:

Getting binaries... AltStore is up to date. AltServer is up to date. netmuxd is up to date. anisette-server is up to date. Making scripts executable... Starting avahi-daemon service... Purging logs... Decompressing required libs for Provision... lib/x86_64/ lib/x86_64/libstoreservicescore.so lib/x86_64/libCoreADI.so Starting supervisord... 2024-09-03 08:22:53,805 INFO Set uid to user 0 succeeded 2024-09-03 08:22:53,807 INFO RPC interface 'supervisor' initialized 2024-09-03 08:22:53,807 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-09-03 08:22:53,807 INFO supervisord started with pid 1 2024-09-03 08:22:54,810 INFO spawned: 'usbmuxd' with pid 70 2024-09-03 08:22:54,812 INFO spawned: 'anisette-server' with pid 71 2024-09-03 08:22:54,813 INFO spawnerr: command at '/altserver/bin/netmuxd' is not executable 2024-09-03 08:22:54,813 INFO spawnerr: command at '/altserver/bin/AltServer' is not executable 2024-09-03 08:22:54,817 WARN exited: anisette-server (exit status 126; not expected) 2024-09-03 08:22:56,027 INFO success: usbmuxd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-09-03 08:22:56,028 INFO spawned: 'anisette-server' with pid 73 2024-09-03 08:22:56,029 INFO spawnerr: command at '/altserver/bin/netmuxd' is not executable 2024-09-03 08:22:56,029 INFO spawnerr: command at '/altserver/bin/AltServer' is not executable 2024-09-03 08:22:56,033 WARN exited: anisette-server (exit status 126; not expected) 2024-09-03 08:22:58,246 INFO spawned: 'anisette-server' with pid 74 2024-09-03 08:22:58,247 INFO spawnerr: command at '/altserver/bin/netmuxd' is not executable 2024-09-03 08:22:58,247 INFO spawnerr: command at '/altserver/bin/AltServer' is not executable 2024-09-03 08:22:58,252 WARN exited: anisette-server (exit status 126; not expected) 2024-09-03 08:23:01,462 INFO spawned: 'anisette-server' with pid 75 2024-09-03 08:23:01,463 INFO spawnerr: command at '/altserver/bin/netmuxd' is not executable 2024-09-03 08:23:01,463 INFO gave up: netmuxd entered FATAL state, too many start retries too quickly 2024-09-03 08:23:01,463 INFO spawnerr: command at '/altserver/bin/AltServer' is not executable 2024-09-03 08:23:01,463 INFO gave up: altserver entered FATAL state, too many start retries too quickly 2024-09-03 08:23:01,467 WARN exited: anisette-server (exit status 126; not expected) 2024-09-03 08:23:01,674 INFO gave up: anisette-server entered FATAL state, too many start retries too quickly

Thanks for the help in advance.

[dreth]

you should make the binaries executable, this should've been done automatically by the image, did you run it in privileged mode?

you should use sudo to run the container

This should be enough, otherwise just make the binaries executable by going to the project's bin directory and doing sudo chmod +x ./*. Careful running this command in the wrong directory.

[TheRealZGYT]

So far no luck. The container is running in privileged mode, made the binaries executable and ran with sudo, also tried chmod. Same log every time the container starts. The error log for anissete just says that the permission denied.

Not really sure what the problem could be.

[dreth]

If you're using docker compose have you tried rebuilding with no cache when rerunning the stack?

sudo docker compose up -d --build --no-cache

[TheRealZGYT]

Yeah, also tried force recreate but the problem persists.

[dreth]

have the binaries in bin been downloaded for the correct architecture? what's this system's architecture?

[TheRealZGYT]

Yes, system is x86_x64 and made sure the correct binaries were downloaded. Still getting

stdbuf: failed to run command ‘/altserver/bin/anisette-server’: Permission denied

On the created error log.

[dreth]

is this the only error youre getting now? are the other processes spawned successfully?

[TheRealZGYT]

It's both, should've mentioned that the first one I sent is the console log and that the error log the container creates is the one I sent on last comment.

[dreth]

sorry im replying to this so late, it's been busy, are you still having this issue?

I would try to cleanup your docker images, note that this command is kinda powerful docker system prune -a and then maybe i would start again and delete the repo - then clone again and follow the instructions always using sudo

I'm not sure if there's some kind of permission limitation in Unraid, I myself have never used it, but from what I can gather it would simply seem like the binaries might have never been made executable and I'm not sure why doing so in your host system didn't make a difference

If nothing works maybe try running without the cgroup mount: /sys/fs/cgroup:/sys/fs/cgroup:ro

Or potentially other root system mounts to see if that makes any difference