Hung at 'Updating Project Zomboid Server...'

[CoryRamsey]

The image seems to be hung at "Updating Project Zomboid Server..."

I've pulled the latest image, created the necessary directories, and launched with minimal environment variables as described in the documentation.

Host machine is Ubuntu 20.10

[Renegade-Master]

I can't tell you what the issue is if you do not include any information. Please do not delete the provided template when creating an issue. I created that template to help me to understand your problem.

[CoryRamsey]

Describe the issue The container hangs at "Updating Project Zomboid Server... "

To Reproduce Steps to reproduce the behavior:

Followed bare minimum instructions:

1. Created ZomboidConfig and ZomboidDedicatedServer directories
2. Ran latest image from dockerhub with command: docker run --mount type=bind,source="$(pwd)/ZomboidDedicatedServer",target=/home/steam/ZomboidDedicatedServer --mount type=bind,source="$(pwd)/ZomboidConfig",target=/home/steam/Zomboid --publish 16261:16261/udp --publish 16262:16262/udp --network common --name zomboid-server docker.io/renegademaster/zomboid-dedicated-server:latest
3. See attached process and result in screenshot below

Expected behavior The server to continue starting

Screenshots

Desktop (please complete the following information):

• OS: Description: Ubuntu 20.10 / 5.8.0-63-generic
• Docker Version: Docker version 20.10.2, build 20.10.2-0ubuntu1~20.10.1
• Image Version: Dockerhub Latest - ID 85f250a74287

Additional context Since I have several networks on this server, I thought perhaps the container wasn't hitting the internet. I created a docker network bridge named common. I've added only this argument to the bare minimum launch command. If it is not clear, the same issue occurs without the explicit network definition. The common network is bridged properly and hits the internet with other containers.

The intention of this issue is to be informative more than anything. I've created my own docker image in the meantime that is working for me. If there is nothing obvious I'm missing or immediately known that would solve the issue, I'd be more than happy to help dig in and troubleshoot what is going on if there is interest in understanding for the purpose of ensuring others do not run into this issue in the future. I didn't spend much time troubleshooting initially, as that defeats the purpose of trying to use this docker image, in my case.

I've also tried this image and older versions of the image on various machines and configurations, but the container continues to stall at the same stage. I've also tried using docker-compose with applicable environment variables all filled in both on the image and by building it, but it seems to be getting hung on the update step before any of these variables would be a factor.

Also, sorry for not using the template.

[Renegade-Master]

Hey, thanks for taking the time for provide the information.

There is an ongoing issue at the moment that I am not entirely sure about the cause of.

Your issue seems different though. It does seem like it either

• doesn't have access to the Internet
• is still downloading steamcmd for some reason

For now my time is occupied with fixing the other issue, and maybe that will fix this. Generally though, I would attribute network issues like that down to the deployer/environment, as the closest thing to networking configured in this image is a call to hostname -I to determine the listening address.

[CoryRamsey]

Ok, that's helpful info that you don't know anything immediate off-hand that it would be. This server I've mostly been trying on has quite the convoluted network configuration in a data center. Networking was my first thought, too, which is why I made a custom docker network that I verified worked with other containers. But having the same issue on two other machines at different locations made me start to think otherwise. I haven't looked at the script much yet, but I strongly suspect it is related to steam, given it is stuck on the update part. With this info in mind, when I get a chance I'll take another in-depth poke at it to see if I can figure out what's happening and report back.

[jhthorp]

I am having this same issue on a config that currently works on 1.6.1 but when upgraded to 2.0.1 it hangs on the update. I am running my server on an X64 Ubuntu 22.10 server. The network configuration is the default. I will be staying on 1.6.1 until this is able to be understood.

From looking over the changes, the only difference that seems notable is that the base image for steamcmd was bumped a few versions.