Startup Issue with Windrose - Windrose: Wine not Implemented

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Deimos’ v2.7.2.2 (Mainline)
Virtualization Docker
Application Windrose
Module GenericModule
Running in Container Yes
Current State Starting

Problem Description

Issue

I am trying to play on my Windrose server that has been working for days now, al of a sudden ‘wine’ is not implementing. Starting the instance is not working

Reproduction Steps

  • Delete .wine folder and recreate on startup
  • Ask assistance from Kodee
  • Checked Windrose Forums for information

I’m also having similar issues, it was working just yesterday, and now today the server cant start also refuses to update.

Edit:

After some testing, it seems to be all of my servers that use Wine that’s not working.

Servers i’ve tested:

7 Days to die (doesn’t use Wine) = Works with no issue

Palworld (uses Wine) = wine: socket : Function not implemented

Space Engineers (uses Wine) = wine: socket : Function not implemented

Windrose (uses Wine) = wine: socket : Function not implemented

┏━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Key                  ┃ Value                                 ┃
┣━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ Operating System     ┃ Linux - Debian GNU/Linux 13 on x86_64 ┃
┃ Product              ┃ AMP 'Deimos' v2.7.2.0 (Mainline)      ┃
┃ Virtualization       ┃ VMware                                ┃
┃ Application          ┃ Application Deployment                ┃
┃ Module               ┃ ADSModule                             ┃
┃ Running in Container ┃ No                                    ┃
┃ Current State        ┃ Indeterminate                         ┃
┗━━━━━━━━━━━━━━━━━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

This is the cause: Docker 29.4.2 SteamCMD Issue

1 Like

Thank you for letting me know it was a docker issue.

Here for anyone who may need to downgrade and are on Debian 13: BACKUP BEFORE DOING AND USE WITH CAUTION!!!

Downgrading Docker to 29.4.1 on Debian 13 (Trixie)

1. Stop Docker Services

Stop the daemon and sockets to prevent data corruption during the downgrade.

sudo systemctl stop docker.socket
sudo systemctl stop docker

2. Identify Exact Version String

Check the available versions in your repository to confirm the exact string (e.g., 5:29.4.1-1~debian.13~trixie).

apt-cache madison docker-ce

3. Run the Downgrade Command

Use the --allow-downgrades flag. Replace the version strings below if apt-cache showed a slightly different naming convention for your repo.

sudo apt-get install --allow-downgrades -y \
  docker-ce=5:29.4.1-1~debian.13~trixie \
  docker-ce-cli=5:29.4.1-1~debian.13~trixie \
  containerd.io \
  docker-buildx-plugin \
  docker-compose-plugin

4. Pin the Version

Prevent apt upgrade from automatically updating Docker back to the newer version.

sudo apt-mark hold docker-ce docker-ce-cli

5. Restart and Verify

sudo systemctl start docker
docker --version

How to Re-enable Updates (Unpinning)

If you later decide you want to upgrade Docker to the latest version again, follow these steps:

1. Remove the Hold

This tells apt that it is allowed to modify these packages again.

sudo apt-mark unhold docker-ce docker-ce-cli

2. Upgrade to Latest

Run a standard update and upgrade to pull the newest version available in the Debian 13 repos.

sudo apt-get update
sudo apt-get upgrade docker-ce docker-ce-cli
3 Likes

That certainly helped me, Thank you.