Many thanks to the battlefieldbadcompany2mase project by flyer8472 for the great project, which enabled me to build these Docker-Images in the first place.

This projects contains two docker-images:

• The master-server which is needed by the client to handle the user-account and manages the server-list
• The game-server which the clients can connect to for gaming

With this both images you are able to run your own Battlefield Bad Company 2 LAN-Server.

The easiest way to start your own BFBC2 LAN-Server is to use docker-compose and run it with

docker-compose up -d

this command will start up both servers with default configurations.

alternatively you can run the docker-images manually:

# master-server
docker run \
    -d --net=host \
    quay.io/docker-gameserver/bfbc2-master-server

# game-server
docker run \
    -d --net=host \
    quay.io/docker-gameserver/bfbc2-server

To be able to connect to your bfbc2-server you have to add the two files bfbc2.ini and dinput8.dll to your installed game-root-folder. This files are included in the Bc2emu_V09.rar (download) inside of the "Crack - Copy to client root"-directory. Edit the line host=127.0.0.1 in the bfbc2.ini and fill in the ip of your server.

In the game simply create a new account with dummy-data (the account data are saved in plain-text in the database-directory mounted to the master-server...)

Inside of the Bc2emu_V09.rar file is also included a readme.txt for detailed instructions.

If you start the server without a database-volume the registered accounts are non-persistent and have to be recreated every time the container is recreated.

To enable persistence you have to create a local database folder and mount it to the docker-container (this is enabled by default in the docker-compose.yaml):

mkdir ./database
docker run \
    -d --net=host \
    -v "./database:/home/bfbc2/database" \
    quay.io/docker-gameserver/bfbc2-master-server

You can overwrite the config.ini with your own by adding a custom config.ini as volume:

docker run \
    --rm -ti --host=net \
    -v ./database:/home/bfbc2/database \
    -v ./config.ini:/home/bfbc2/config.ini \
    quay.io/docker-gameserver/bfbc2-master-server

or edit the docker-compose.yaml and uncomment the - "./custom-config.ini:/home/bfbc2/config.ini" line.

The default maplists can be overwritten by mounting your own maplist to /home/bfbc2/server/maplists/<gamemode>.txt

docker run \
    --rm -ti \
    -v "./custom_rushmaplist.txt:/home/bfbc2/server/maplists/rush.txt" \
    quay.io/docker-gameserver/bfbc2-server

Naturally you do not have to use the pre-build images from docker-hub. Simply build your own images:

docker build -t bfbc2-master-server ./master-server
docker build -t bfbc2-server ./game-server

Currently the docker-containers are startet in host-networking mode. Until now I was not able to run the containers with simple port-mappings. Neither the registration on the master server can be completed, nor can the game servers be found.

I am grateful for further tips

The remote administration via the SERVER_ADMIN_PORT / SERVER_ADMIN_PASSWORD is currently untested. Feel free to add further instructions to the readme ;)