Closed HalfEatenPie closed 3 years ago
Figured out what the issue was.
I tried running the docker file without the /rust.env parameter. It seems there's an error with the following startup argument:
RUST_SERVER_STARTUP_ARGUMENTS=-batchmode -load -logfile /dev/stdout +server.secure 1
logfile
the location /dev/stdout
does not exist which is causing the failure/error.
I'm not exactly sure how the original instructions were built to support this, but they may need to be updated to reflect the location /dev/stdout may no longer exist or be available in the most recent docker image.
Facepunch updated Rust to use a newer version of Unity, which ones again broke existing linux compatibility, including stdoud/stderr support. This is why the image no longer uses -logfile /dev/stdout
by default.
Ahh shucks. Got it thanks for the speedy response. I also realized above I have two RUST_SERVER_MAXPLAYERS
when I meant the second one to be the server website environment variable.
Regardless, cheers! Thanks for building this!
Facepunch updated Rust to use a newer version of Unity, which ones again broke existing linux compatibility, including stdoud/stderr support. This is why the image no longer uses
-logfile /dev/stdout
by default.
So how to setup correct log rotation?
-logfile -
works for me
Describe the bug Unable to start rust-server with base configuration due to an error that seems to be resolved previously but is recurring now. #59
To Reproduce Steps to reproduce the behavior:
/usr/bin/docker run -p 28015:28015 -p 28015:28015/udp -p 28016:28016 -p 8080:8080 --name rust-server --env-file /rust.env -v /rust:/steamcmd/rust --rm didstopia/rust-server
Expected behavior Vanilla Rust server is up
Screenshots Here is an output of the console logs:
Environment (please complete the following information):
Additional Information:
This is the contents of my
rust.env
file.