Closed Stultusaur closed 8 months ago
Can you share a bit more detail what hardware are you using, do you run the container from a HDD/SSD/NVME? I assume this happens only on the first start from the container correct?
EDIT: I've pushed a update to the container, please update the container itself and see if that fixes the issue on your system.
Can you share a bit more detail what hardware are you using, do you run the container from a HDD/SSD/NVME? I assume this happens only on the first start from the container correct?
EDIT: I've pushed a update to the container, please update the container itself and see if that fixes the issue on your system.
Yes, your update resolved the issue, I created a new container,
To answer your question, I am running CentOS VM from ESXi on a SSD (Non NVMe) And after the ShooterGame.log file was created manually, it would start fine after that, and would also truncate the logs fine, it was just during initial setups that caused problems :)
Thank you for resolving the problem.
I am having an issue with my docker container for Ark Survival Ascended.
I am getting a line: tail: cannot open '/serverdata/serverfiles/ShooterGame/Saved/Logs/ShooterGame.log' for reading: No such file or directory tail: no files remaining
After that message, it resets the docker container, If I manually created the ShooterGame.log file, setting the permissions correctly, it then runs without issue. I get the below message after creating the shootergame.log file: tail: /serverdata/serverfiles/ShooterGame/Saved/Logs/ShooterGame.log: file truncated Then the server starts.
Unsure why this is happening,
Are you able to explain this problem?