yanwenkun / barotrauma-server-docker Goto Github PK

The Problem

To specify admins in the slim tag, we need to edit the Data/clientpermissions.xml file. Upon restarting the server by recreating the container, this file is reset to the default value of:

<?xml version="1.0" encoding="utf-8" ?>
<ClientPermissions>  
</ClientPermissions>

Reproducable Steps

compose.yaml

version: "3"
services:
  barotrauma:
    image: yanwk/barotrauma-server:slim
    restart: unless-stopped
    ports:
      - "27015:27015/udp"
      - "27016:27016/udp"
    volumes:
      - "./data:/home/runner/Steam/steamapps/common/Barotrauma Dedicated Server"

1. Create compose.yaml
2. Run docker compose up -d
3. Wait for server to be ready
4. Run docker compose down
5. Edit Data/clientpermissions.xml
6. Run docker compose up -d
7. Notice that Data/clientpermissions.xml is reset to default value

Temp Fix

Make the file read-only. I achieve this by adding this to my compose file:

  volumes:
      - "./data/Data/clientpermissions.xml:/home/runner/Steam/steamapps/common/Barotrauma Dedicated Server/Data/clientpermissions.xml:ro"

Hi. I will try to setup barotrauma server today and I found your container. Few months ago, we ware playing valheim using dockerized server. This image has periodic backup option: https://github.com/lloesche/valheim-server-docker
Maybe you want to add similar feature to your barotrauma container?
For now I will use some local cronjob to zip all server files, but it will be nice if container can do it for me just by setting pariodic_backup flag to true.

If an update to steamcmd exists since the last slim docker image was pushed to Docker Hub, the server will fail to start. For example, using the digest for the latest slim image:

docker run --rm yanwk/barotrauma-server@sha256:5611317814f2e15df9eefa515d9e4819f5eb361e61df38e4d3677c777b10906e
Redirecting stderr to '/home/runner/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Downloading update (182 of 57,751 KB)...
<SNIP>
[ 99%] Downloading update (57,751 of 57,751 KB)...
[100%] Download complete.
[user ~]$

I believe this is a result of the update requiring root privileges, although steamcmd is not very verbose about it. A simple fix would be to include && steamcmd +quit in the Dockerfile CMD before doing su runner. A more involved solution would be to install steamcmd as the non-root user, but that seems like a lot of work.

  Server started etworking. Manual port forwarding may be required. If players cannot connect to the server, you may want to use the in-game hosting menu (which uses SteamP2P networking and does not require port forwarding).
Session terminated, killing shell...src/tier1/fileio.cpp (5315) : m_vecRegisteredWriters.Count() == 0
src/tier1/fileio.cpp (5315) : m_vecRegisteredWriters.Count() == 0
 ...killed.
Redirecting stderr to '/home/runner/Steam/logs/stderr.txt'
^[[3;1R^[[2;1R^[[3;1R^[[4;1R[  0%] Checking for available updates...

It starts fine the first time, but if you stop and restart, it crashes here, every time.

using slim on Ubuntu 18.04 LTS

EDIT: this is before any configuration changes, vanilla

Hi. This issue is basically a cross-post of the issue I made on the Barotrauma repo, since I'm not sure if this is an issue with the Docker image or the dedicated server executable itself. In short, the problem is that content packages specified in the user_config.xml aren't being loaded by the server at launch — but please see the linked issue for the full description of the problem.

I'm using the slim variant of the Docker image, using docker compose to launch it.

If someone using this Docker image to host a dedicated server with mods enabled could share their full user_config.xml so I can compare it with mine, that'd be a useful next step to investigate the issue, I think.

Thanks in advance for any help! 🙏