https://github.com/phistrom/l4d2-docker
Dockerized Left 4 Dead 2 dedicated server
https://github.com/phistrom/l4d2-docker
left4dead2
Last synced: 8 months ago
JSON representation
Dockerized Left 4 Dead 2 dedicated server
- Host: GitHub
- URL: https://github.com/phistrom/l4d2-docker
- Owner: phistrom
- Created: 2021-06-13T04:38:23.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2021-06-14T05:53:55.000Z (about 5 years ago)
- Last Synced: 2024-12-27T00:12:00.647Z (over 1 year ago)
- Topics: left4dead2
- Language: Shell
- Homepage: https://hub.docker.com/r/phistrom/l4d2
- Size: 2.93 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Dockerized Left 4 Dead 2 Dedicated Server
## Usage
You can start a Left 4 Dead 2 dedicated server with nothing else installed
except Docker by running:
```sh
docker run -itd --net=host --name l4d2 -v /srv/l4d2:/l4d2 phistrom/l4d2
```
This will run the server with the default parameters of `-port 27015` and
`-secure`. The initial run of this container will download around 9.2GB of
data before it will start. Subsequent runs will be much, much faster (provided
you mount the same directory for `/l4d2` each time).
Any additional parameters you specify will be passed along to the `srcds_run`
command. For example, the following is equivalent to the first example:
```sh
docker run -itd --net=host --name l4d2 -v /srv/l4d2:/l4d2 phistrom/l4d2 -port 27015 -secure
```
To save time, the `steamcmd` runs `+app_update` *without* `validate`. To verify
that the files for the dedicated server are not corrupt, pass in a non-empty
**`VALIDATE`** environment variable to the container like this:
```sh
docker run -itd --net=host --name l4d2 -v /srv/l4d2:/l4d2 -e VALIDATE=1 phistrom/l4d2
```
This is equivalent to running `steamcmd +app_update 222860 validate` before
starting `srcds_run`.
Be sure to mount the container's `/l4d2` directory or else it will need to
redownload all the game files and Steam client every time.
To see what your server is doing, you can run `docker logs -f l4d2`.