azerothcore / azerothcore/acore-docker

ac-eluna-ts-dev-1 | touch: index.ts: Permission denied

Open
#46 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
302
Forks
102
PR merge metrics
No merged PRs in 30d

Description

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.)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with docker-compose.yml and the ac-eluna-ts-dev service, then reproduce the setup described in the issue while comparing behavior with and without privileged: true on ac-worldserver. Trace why the service cannot touch index.ts; done means the service starts without the permission error or restart loop, with the documented setup clarified.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, typescript
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.