Hi,
I’m trying to install the Emperor server to run the AC server on an RPi 3 / Jetson Nano. Still, I couldn’t figure out whether I could install Steam there? as it needs to refer to the AC manager installation in a Steam folder, according to the installation guide.
Anyone have attempted to do this?
Hi,
We do have multiple users running ACSM v2 on Pis, so you should definitely be able to get this running.
You don’t need to have Steam or the AC server/manager installed in order to run ACSM v2, so you can disregard those steps in you’re installing v2. This is because v2 uses our custom server that we built ourselves so it can operate completely standalone.
We still usually recommend installing the original server to get instant access to the included tracks/cars/weathers, but it isn’t necessary for a “barebones” install, you’ll just need to upload content yourself from the Content pages of the Manager instead after startup.
I hope that helps, please let us know if you have any further questions!
Thanks,
Henry
Hi @freddi, @Hecrer did you manage to get it work? I’m getting a permission denied issue inside the docker container while trying to create the instance.
I’m using acsm_v2.4.6_linux-arm64 package, and I think the binaries are not correct built for ARM. If I run:
file assetto-multiserver-manager
I get:
assetto-multiserver-manager: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=VGiA7hkzMYFkXfgURDgQ/ch4iwz9k20uJJvFRHnLO/1OmwoOMmh5bJZB5mTwCF/EZZOpOrvgdq6Q5qMbCEU, stripped
that is ok, but when try to run I get permission denied.
If I run:
bash assetto-multiserver-manager
I get:
assetto-multiserver-manager: assetto-multiserver-manager: cannot execute binary file.
And when trying to run it via docker-compose, I get the same permission denied error inside the container.
And if you try to the binary directly from RaspbianOS shell via ./assetto-multiserver-manager you get:
bash: ./assetto-multiserver-manager: Permission denied
Please can you run the following command on your machine and send us the output?
$ uname -a
Sometimes permission denied errors can occur due to incorrect permissions on the executable itself. Please can you try running:
chmod +x server-manager
chmod +x assetto-multiserver-manager
And see if this helps?
I can confirm that the binaries for the Server Manager are built correctly for arm64.
If this doesn’t work, the following may do:
What kind of filesystem are you running ACSM on? In general on linux we would recommend a linux native filesystem (e.g. ext4, btrfs), and not something more windows native such as FAT or NTFS.
Could you try moving the executable file to a different location (or different drive) and see if this helps?
The output of uname -a:
5.15.0-203.146.5.1.el8uek.aarch64 #2 SMP Thu Feb 8 18:41:55 PST 2024 aarch64 aarch64 aarch64 GNU/Linux
The filesystem:
/dev/sda4 97675264 419430366 321755103 153.4G Linux filesystem
The permissions:
-rwxrwxrwx. 1 opc opc 29622424 Jul 2 16:36 assetto-multiserver-manager
-rwxrwxrwx. 1 opc opc 42336408 Jul 2 16:36 server-manager
The output of the docker container:
time=“2025-07-02T16:48:53Z” level=fatal msg=“Could not start assetto corsa multiserver instance” error=“fork/exec ./server-manager: permission denied”
I think the problem is related to the entrypoint, in the docker compose says that you have to select server-manager or assetto-multiserver-manager as entrypoint, but the Dockerfile has server-manager defined as entrypoint. Even if I change in the Dockerfile and rebuild the image of the container and launch again the docker compose with both entrypoint (Dockerfile and docker compose) as assetto-server-manager, I get the same error:
time=“2025-07-02T16:48:53Z” level=fatal msg=“Could not start assetto corsa multiserver instance” error=“fork/exec ./server-manager: permission denied”
Where you can see it’s still trying to run the server-manager instead of assetto-server-manager.
Furthermore, inside the SERVER_00, SERVER_01…I cannot see the assetto-server-manager binary copied but the server-manager.
I’ve tried to copy it manually with the same result, it’s always expecting the server-manager to be run.
If I put in the Dockerfile and in the docker compose server-manager as standalone server, it works…so, definetely something is happening with the multiserver as the container always tries to find server-manager
ok, issue solved.
The problem was that I had mounted my partition withoud adding the attribute exec in the /etc/fstab file.
I’ve added it, rebooted and now it works!
Thank you for your help and sorry for the inconvenience!!!