After following the instructions for the ACore docker compose setup, I wound up with the ac-eluna-ts-dev service (which I didn't touch) producing these failure messages:
ac-eluna-ts-dev-1 | touch: index.ts: Permission denied
ac-eluna-ts-dev-1 exited with code 1 (restarting)
ac-eluna-ts-dev-1 exited with code 1 (restarting)
ac-eluna-ts-dev-1 exited with code 1 (restarting)
ac-eluna-ts-dev-1 | touch: index.ts: Permission denied
ac-eluna-ts-dev-1 | touch: index.ts: Permission denied
ac-eluna-ts-dev-1 exited with code 1 (restarting)
(Granted, I did modify docker-compose.yml by commenting out privileged: true on the ac-worldserver service, but I don't see why that would affect the ac-eluna-ts-dev service and, if the only side-effect is Can't set process priority class, error: Permission denied and some possible latency spikes that I have to manually mitigate, I consider that an acceptable trade off for limiting its exploitability.)
After following the instructions for the ACore docker compose setup, I wound up with the
ac-eluna-ts-devservice (which I didn't touch) producing these failure messages:(Granted, I did modify
docker-compose.ymlby commenting outprivileged: trueon theac-worldserverservice, but I don't see why that would affect theac-eluna-ts-devservice and, if the only side-effect isCan't set process priority class, error: Permission deniedand some possible latency spikes that I have to manually mitigate, I consider that an acceptable trade off for limiting its exploitability.)