Fork: 0
mark / docker-doom

A fork of https://github.com/mccarrmb/docker-doom with my own improvements

Download ZIP 46 commits
Transfer to URL with SHA
latest commit 0ee32c907a
@Whitey McCarragher Whitey McCarragher authored on 22 Feb 2018
bin synced env variables 7 years ago
builder clarified comments 7 years ago
config changed to default 7 years ago
iwad added more shareware iwads 7 years ago
player added player management files 7 years ago
templates cleaned up templates 7 years ago
wad added placeholder for wad dir 7 years ago
.gitignore added vim and macos crap to gitignore 7 years ago
Dockerfile Dockerfile actually works now 7 years ago
README.md fleshed out README 7 years ago
build-docker-doom.sh created build script 7 years ago
docker-doom.sh added restart policy 7 years ago
README.md

docker-doom

A Zandronum server configuration and deployment tool utilizing a Docker-based back-end.

Usage

  1. Install Docker
  2. Run build-docker-doom.sh
  3. Run docker-doom.sh
  4. Connect to your dumb shareware Doom server

F.A.Q.

Q. What if I want to customize this container to run a different Doom engine game?

A. You're smart enough to create a GitHub account. You figure it out. ...In the mean time, I'm working on a tool to help with it.

Q. What if I'm on Windows?

A. You can try building the image manually, but I currently don't have any PowerShell helper scripts to do this for you. Be aware that this image is Linux-based which means that it won't run alongside Windows-based containers.

Q. Why wouldn't I just run these servers locally instead of firing up containers?

A. You could totally do that. In fact, there really isn't much of a difference. I prefer to use Docker, though, because it saves me the hassle of trying to write clever UpStart/SystemD/rc.d-type service scripts and jobs. All I have to do is add --restart always to the run line and the Docker daemon will take care of keeping the servers running.

There is currently a game-breaking bug in the Linux version of Zandronum 3.0
The bug is detailed here, https://zandronum.com/tracker/view.php?id=2775. The short story is that the Linux executable does not calculate resource hashes correctly on its end. This means that if you run a dedicated Linux server, Windows and macOS clients will get kicked because the hashes they send will not match what the Linux server came up with. Since this project uses Docker to set up servers, this bug puts the project in quite a pickle.