Closed philx02 closed 3 years ago
If, at any point, you run the server as root (docker-compose.scratch.yml
/ valheim-dedicated-scratch
) the container will write out the logfiles as the root user. Since these are in a shared & volumed directory and they don't get automatically cleaned up, when you later run the service normally (docker compose up
) then the less privileged steam user can't write over the logfiles that root created earlier, hence the permissions error you ran into.
I would suggest just cleaning up the files in valheim-data/
that were written as root before switching back to using the service in a non-root mode.
I was running this dedicated server fine until I did a pull from the recent changes and when I try to start the server interactively with
docker-compose -f docker-compose.scratch.yml run --service-ports valheim-dedicated-scratch
and then run runserver.sh, it works fine, but when I try to run it with
docker-compose up
I got this output (near the end):
Apparently we need to be root in the container and we are not?