Developmentįirst set up Docker Desktop on Windows (WSL2).ĭownload the assets (see assets.txt) and put them in the images/*/assets/ folder so you don't need to redownload them on each build. If you are not using a container registry then the images need to be built on the host first. Place the docker-compose.yml on the host and run docker-compose up -d -remove-orphans to create the containers. Image: nihlen/bf2-docker/bf2hub-pb-mm-bf2cc Not practical since you can't play online but it can be used as a base. The basic image to run a Battlefield 2 server. For this use case I prefer using Docker Compose, an example is listed further down. Running multiple servers on the same host can be done by changing the ports in the environment variables and the mapped host port. To use these images on a remote host like a VPS you can either use the snippets below to build and run or you can build the images locally and then push them to a container registry like Docker Hub or Azure Container Registry (public or private). If you want to have full visibility of the server files you can also map the /home/bf2/srv folder of the container. Persisted files like settings, logs and demos are put in the /volume directory in the container using symbolic links and should be mapped to a host directory. Initial settings or passwords can be set using environment variables. To create your own, you can copy one of the existing images to use as a base, and then place your custom files in the assets/bf2 folder to overwrite any existing files.
Prerequisitesĭifferent server variations are placed in the images folder. Uses multi-stage builds to keep the image sizes down. The base image is debian:stretch-slim and was tested on Linux containers in Windows 10 WSL2 and Debian 11. Dockerized Battlefield 2 server based on insanity54/bf42-dock.
0 kommentar(er)
