Closed bennyzen closed 3 years ago
Hm I can't recreate this error on my side..
Please comment your docker run
/ docker create
command, so that I can look further into it.
Funny, but I can't reproduce the issue today either. Something must have changed. But hey, it works now. Thank you for your patience.
Simply restarting the container seems to break things. After a restart, the logs folder seems missing.
Doing something like
docker logs -f ts3
results in:repeated continously.
The container comes back up, but the logs are gone or just filled with the statements above.
I can't figure out how to fix this, as the logs folder is present and readable .