-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate Windows support #14
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Running docker on windows, I cloned the repo (with # It complains that the directory doesn't exist, if we don't manually create it
# I am running the modded server, which uses the 'rust-server-modded' subfolder.
mkdir rust-server-modded
docker build -t didstopia/rust-server:latest .
# Run a modded server
# I am running this on the same PC as the game, to make sure it is working right now
# I have removed the '--network=host' arg just for simplicity.
docker run -p 0.0.0.0:28215:28015 -p 0.0.0.0:28215:28015/udp -p 28216:28216 -p 0.0.0.0:8082:8080 -m 2g -v ${pwd}/rust_data_modded:/steamcmd/rust -e RUST_SERVER_STARTUP_ARGUMENTS="-batchmode -load -nographics -logfile /dev/stdout +server.secure 1 +server.saveinterval 60" -e RUST_RCON_PORT=28216 -e RUST_UPDATE_CHECKING=0 -e RUST_BRANCH="public" -e RUST_UPDATE_BRANCH="public" -e RUST_OXIDE_ENABLED=1 --name rust-server-modded -d didstopia/rust-server:latest
docker logs -f rust-server-modded
I ran this, and the container built fine, then ran fine. So I would say that this should be good to go on windows to be honest, almost as is. Only issue I am facing right now is that when I try to connect in game with Auth was working fine after starting up the container a second time. Looks like Auth was an issue with my end/steam. Edit:
|
Have this issue too, and I'm attempting to run this docker on macOS. Output:
|
Sounds like it's running out of resources (memory, CPU, disk space), with memory being the usual culprit. The bigger the map, the more resources the container will need. |
FWIW; I opened all of the shell scripts in vscode and pressed |
Look at running the container on Windows and see what the major pain points there are, especially regarding volumes (filesystem, paths and permissions).
The text was updated successfully, but these errors were encountered: