Cannot Run Multiple Valheim Instances on Same Server

[action3]

Hello! I cannot seem to create multiple instances. When I bring the containers up, only one server shows as healthy:

Here is my docker-compose.yml file, with some slight omissions for server details:

version: "3"
services:
  valheim:
    image: mbround18/valheim:latest
    ports:
      - 2456:2456/udp
      - 2457:2457/udp
      - 2458:2458/udp
    environment:
      - PORT=2456
      - NAME=name
      - WORLD=world
      - PASSWORD=password
      - TYPE=BepInEx
      - UPDATE_ON_STARTUP=1
      - TZ=America/New_York
      - PUBLIC=0
      - ENABLE_CROSSPLAY=1
      - AUTO_UPDATE=1
      - AUTO_UPDATE_SCHEDULE=0 1 * * *
      - AUTO_UPDATE_PAUSE_WITH_PLAYERS=1
      - AUTO_BACKUP=1
      - AUTO_BACKUP_SCHEDULE=*/15 * * * *
      - AUTO_BACKUP_REMOVE_OLD=1
      - AUTO_BACKUP_DAYS_TO_LIVE=3
      - AUTO_BACKUP_ON_UPDATE=1
      - AUTO_BACKUP_ON_SHUTDOWN=1
      - AUTO_BACKUP_PAUSE_WITH_NO_PLAYERS=1
    volumes:
      - ./valheim/saves:/home/steam/.config/unity3d/IronGate/Valheim
      - ./valheim/server:/home/steam/valheim
      - ./valheim/backups:/home/steam/backups
  valheimplus:
    image: mbround18/valheim:latest
    ports:
      - 2459:2456/udp
      - 2460:2457/udp
      - 2461:2458/udp
    environment:
      - PORT=2456
      - NAME=name
      - WORLD=world
      - PASSWORD=password
      - TYPE=ValheimPlus
      - UPDATE_ON_STARTUP=1
      - TZ=America/New_York
      - PUBLIC=0
      - ENABLE_CROSSPLAY=1
      - AUTO_UPDATE=1
      - AUTO_UPDATE_SCHEDULE=0 1 * * *
      - AUTO_UPDATE_PAUSE_WITH_PLAYERS=1
      - AUTO_BACKUP=1
      - AUTO_BACKUP_SCHEDULE=*/15 * * * *
      - AUTO_BACKUP_REMOVE_OLD=1
      - AUTO_BACKUP_DAYS_TO_LIVE=3
      - AUTO_BACKUP_ON_UPDATE=1
      - AUTO_BACKUP_ON_SHUTDOWN=1
      - AUTO_BACKUP_PAUSE_WITH_NO_PLAYERS=1
    volumes:
      - ./valheimplus/saves:/home/steam/.config/unity3d/IronGate/Valheim
      - ./valheimplus/server:/home/steam/valheim
      - ./valheimplus/backups:/home/steam/backups
  bepinexfull:
    image: mbround18/valheim:latest
    ports:
      - 2462:2456/udp
      - 2463:2457/udp
      - 2464:2458/udp
    environment:
      - PORT=2456
      - NAME=name
      - WORLD=world
      - PASSWORD=password
      - TYPE=BepInExFull
      - UPDATE_ON_STARTUP=1
      - TZ=America/New_York
      - PUBLIC=0
      - ENABLE_CROSSPLAY=1
      - AUTO_UPDATE=1
      - AUTO_UPDATE_SCHEDULE=0 1 * * *
      - AUTO_UPDATE_PAUSE_WITH_PLAYERS=1
      - AUTO_BACKUP=1
      - AUTO_BACKUP_SCHEDULE=*/15 * * * *
      - AUTO_BACKUP_REMOVE_OLD=1
      - AUTO_BACKUP_DAYS_TO_LIVE=3
      - AUTO_BACKUP_ON_UPDATE=1
      - AUTO_BACKUP_ON_SHUTDOWN=1
      - AUTO_BACKUP_PAUSE_WITH_NO_PLAYERS=1
    volumes:
      - ./bepinexfull/saves:/home/steam/.config/unity3d/IronGate/Valheim
      - ./bepinexfull/server:/home/steam/valheim
      - ./bepinexfull/backups:/home/steam/backups

Here is some output from valheim_server.log (valheim_server.err did not seem to catch anything out of the ordinary):

05/05/2023 13:12:55: Get create world Yggdrasil
05/05/2023 13:12:55:   failed to load Yggdrasil
05/05/2023 13:12:55:  creating
05/05/2023 13:12:55: Considering autobackup. World time: 0, short time: 7200, long time: 43200, backup count: 4
05/05/2023 13:12:55: Creating first autobackup
05/05/2023 13:12:55: Saving backup at: /home/steam/.config/unity3d/IronGate/Valheim/worlds_local/Yggdrasil_backup_auto-20230505131255.fwl
05/05/2023 13:12:55: Using environment steamid 892970
05/05/2023 13:12:55: Using steam APPID:892970
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
05/05/2023 13:12:55: Server ID 90071992547409920
05/05/2023 13:12:55: Authentication:k_ESteamNetworkingAvailability_Waiting
05/05/2023 13:12:55: Steam game server initialized
05/05/2023 13:12:55: Using default prefs
05/05/2023 13:12:55: Valheim version: 0.215.2 (network version 1)
05/05/2023 13:12:55: Worldgenerator version setup:2
ERROR: Shader TextMeshPro/Sprite shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
05/05/2023 13:12:55: Render threading mode:SingleThreaded
05/05/2023 13:12:55: Missing audio clip in music respawn
05/05/2023 13:12:55: Builder started
GetPixel called on an undefined mip (valid values are 0 - 6
Caught fatal signal - signo:11 code:1 errno:0 addr:0x3fb
Obtained 3 stack frames.
#0  0x007f1fb301a520 in __sigaction
#1  0x007f1fb41792c3 in Texture2D_CUSTOM_GetPixelImpl_Injected(ScriptingBackendNativeObjectPtrOpaque*, int, int, int, int, ColorRGBAf&)
#2  0x000000411efe75 in (wrapper managed-to-native) UnityEngine.Texture2D:GetPixelImpl_Injected (UnityEngine.Texture2D,int,int,int,UnityEngine.Color&)

Is there something special I need to do with multiple NICs (I only have a single NIC)? I was assuming since different ports were mapped to each server that this would not be the case. Please let me know what I am doing wrong. Thanks for all of your work you have done on this. It is a great solution!

[coreyaboy]

I'm not in a place where I can get to a computer and properly look at my notes, but least year when II be was trying to setup my multiple instances of a Valheim dedicated server on my Linux box, I ran into a problem that might be relevant.

It doesn't make sense to me that this would be an issue inside docker containers, but as of last year, the Valheim code base (both dedicated server and client) fails spectacularly on systems with more than one nick, or more than one IP address.

If I was faced with your problem, I'd start with focusing on the network side of things. First I'd make sure the containers are not been assigned multiple internal IP addresses. Then I'd try an experiment and swap around the network/port parts of each containers config to see if the stable/unhealthy statuses followed a specific set of port mapping assignments.

Your log shows the healthy container as hand already been up for awhile. Maybe restart the healthy container to see if it suddenly goes unhealthy. If that happens, it's likely something new inside a recent update to the container image. I've also had the occasional container start unhealthy and sort itself out after a few hours.

Good luck!

[coreyaboy]

Another experiment worth considering is finding the triple server docker-compose example that mbround wrote for me in a different thread elsewhere on this board. It worked for be flawlessly. Asv an AB test, knowing if the example config works as is on your system while your config is running into trouble might help you narrow down where to pay attention.

[action3]

Thanks @coreyaboy, this is exactly the template that I based this off of when authoring the docker-compose. I did change the services names to something more user friendly (valheimplus and bepinexfull), as opposed to valheim-02 and valheim-03.

In regards to your first comments, the first server (the healthy one), has been in place for some time now. I have not had an issue with it. I'll check out some of the network config, but Docker chops are limited, hence my post. I did find that the containers are running with different IP addresses after running a docker inspect. Is this what you are referring to? How would I go about rectifying this?

Shouldn't the containers have different IPs?

[coreyaboy]

Thinking about it a bit more, Docker makes my concern about running the Valheim server on a system with multiple network cards completely irrelevant, and my advice on that front might be useless. Those 3 IP addresses are the internal IP addresses that each individual container is assigned by Docker. They should be different.

When I get home tonight, I'll try running your compose file on my home server and report back with how it fares. Maybe the result tells us something? Fair warning, my docker chops are also not that great. I'm just very enthusiastic about Valheim right now.

[action3]

@coreyaboy, I've been looking for decent folks to play with. Do you use Discord? Any luck with the docker-compose? I was able to create the container successfully using 1.3.4 on a fresh server, which is what the referenced template used. I could not get it to work with the latest build. Wondering if you had similar results.

[action3]

I was able to perform a workaround. I'm using three different docker-compose files to create the server instances. I started with a fresh install of Ubuntu 22.04. I learned when I was creating and testing them, it seemed as if the server TYPE variable did not work consistently with the BepInExFull and ValheimPlus parameters. Vanilla and BepInEx seemed to work fine.

I created three different servers - 1x Vanilla and 2x BepInEx. All started and performed their healthchecks successfully. I then went in to one of the BepInEx servers and added variables for mods, which worked. I went into the other and installed ValheimPlus manually. This worked as well. End result on the production machine:

In the end, I'm sure I could now consolidate the docker-compose files, but I would then still have to install ValheimPlus manually again, presumably because of the TYPE variable not functioning as expected. My next goal is to figure out how to do the same thing in Kubernetes or ECS!

[action3]

Another update. Although the ValheimPlus container was shown as healthy, it was not able to accept incoming connections. I can confirm this is a known version issue with ValheimPlus:

valheimPlus/ValheimPlus#791

mbround18/valheim-docker is pulling 0.9.9.11 of ValheimPlus, which is the correct version in production. However, as stated in the link above, this version will not function on the latest version of Valheim 215.2. Although it's not an official release, using ValheimPlus 0.9.9.15 fixes this issue. Link below:

https://www.nexusmods.com/valheim/mods/2323?tab=files

As far as BepInExFull, I am not sure, but I am using the BepInEx parameter instead and it works just fine.