Am i doing something wrong in setup?

[Dragon-Slayer32]

Im using Proxmox to host the server and using a CT i followed the instructions and im have trouble starting the server keeps saying

windrose | [windrose] Checking if Wine prefix is ready...
windrose | [windrose] Wine diagnostics
windrose | [windrose] WINEPREFIX=/home/steam/.wine
windrose | [windrose] WINEARCH=win64
windrose | [windrose] WINEDLLOVERRIDES=mscoree,mshtml=
windrose | [windrose] prefix arch marker=missing
windrose | [windrose] wine version=wine-11.0
windrose | [windrose] kernel32.dll present=no
windrose | [windrose] drwxrwxr-x 2 steam steam 4096 2026-05-01 17:52 dosdevices
windrose | [windrose] drwxrwxr-x 2 steam steam 4096 2026-05-01 17:52 drive_c
windrose | [windrose] Wine prefix check failed, continuing to next attempt...
windrose | [windrose] Wine prefix initialization failed after 2 attempts

Am I missing something I even tried to use a VM but having a hard time installing the docker
please help and thank you in advance

[UberDudePL]

Thanks for the logs — this is a Wine prefix initialization failure, not a game config issue.

The key lines are:

• prefix arch marker=missing
• kernel32.dll present=no

That means Wine prefix creation did not finish.

For Proxmox CPU settings:

• VM: set CPU type to host
  • UI: VM -> Hardware -> Processors -> Type -> host
  • CLI: qm set <VMID> --cpu host
• CT (LXC): there is no CPU type selector like in VMs; CT uses host CPU directly.
  • Verify architecture is amd64:
    • pct config <CTID>
  • If needed:
    • pct set <CTID> -arch amd64

Then run:

1. docker compose down
2. rm -rf ./steam-home/.wine
3. docker compose up -d
4. docker compose logs -f windrose

If it still fails, switch to staging image tag and retry.

If you are running Docker inside a Proxmox CT and still see Wine init issues, moving to a Proxmox VM is usually the most reliable path.

Try to enable Nesting for CT as well

[UberDudePL]

hey @Dragon-Slayer32,

please try below:

Wine socket: Function not implemented in Docker — Root Cause & Fix

Overview

When running a Wine-based Docker container (e.g. Windrose dedicated server), the following sequence of errors appears in logs and causes the Wine prefix to fail initialization after two attempts[cite:3]:

wine: socket : Function not implemented
wineboot completed in 0s
kernel32.dll present=no
prefix arch marker=missing
Wine prefix initialization failed after 2 attempts

This document explains the root cause and provides actionable fixes.

---

Root Cause

seccomp Profile Blocking AF_ALG Socket

Docker's default seccomp profile blocks certain socket address families, including AF_ALG (address family 38)[cite:2][cite:3]. Modern Wine versions (9+, including Wine 11.7 Staging as shown in the logs) attempt to create an AF_ALG socket during wineserver startup for internal communication. When Docker's seccomp profile intercepts this syscall, it returns ENOSYS — "Function not implemented"[cite:2].

Failure Cascade

The wine: socket : Function not implemented error is not merely cosmetic — it breaks the entire Wine prefix initialization chain[cite:3]:

1. wineserver fails to start properly due to blocked socket syscall
2. wineboot runs but cannot communicate with wineserver → exits in 0 seconds (normal init takes 20–60s)
3. Wine cannot write system registry or populate drive_c/windows/
4. kernel32.dll is never installed → kernel32.dll present=no
5. Prefix architecture marker (system.reg or windows directory) is absent → prefix arch marker=missing
6. Script retries once more, fails again → Wine prefix initialization failed after 2 attempts

Key diagnostic signal: wineboot completed in 0s is a reliable indicator that wineserver did not respond. A healthy first-time prefix initialization takes 20–60 seconds[cite:3].

Additional Factor: Proxmox LXC Nesting

If the Docker host itself runs inside a Proxmox unprivileged LXC container, the syscall restriction is compounded — the LXC security layer and Docker's seccomp profile both filter the same calls[cite:4]. This makes the issue more likely to appear even on Docker configurations that otherwise work on bare-metal hosts.

---

Fixes

Option 1: Disable seccomp (Quick Verification)

Add the following to your docker-compose.yml to confirm seccomp is the cause:

services:
  windrose:
    security_opt:
      - seccomp:unconfined

This disables all seccomp filtering for the container. Do not leave this in place on production or publicly exposed servers. Use it to verify the fix, then move to Option 2.

Option 2: Custom seccomp Profile (Recommended)

Create a targeted seccomp profile that allows only the specific AF_ALG socket call while keeping all other restrictions intact[cite:3].

Step 1 — Download Docker's default seccomp profile:

curl -o /etc/docker/seccomp/default-plus-afalg.json \
  https://raw.githubusercontent.com/moby/moby/master/profiles/seccomp/default.json

Step 2 — Add the following entry to the syscalls array in the JSON:

{
  "names": ["socket"],
  "action": "SCMP_ACT_ALLOW",
  "args": [
    { "index": 0, "value": 38, "op": "SCMP_CMP_EQ" }
  ]
}

Step 3 — Reference the profile in docker-compose.yml:

services:
  windrose:
    security_opt:
      - seccomp:/etc/docker/seccomp/default-plus-afalg.json

---

Verification

After applying the fix, restart the container and check logs for:

Indicator	Broken state	Fixed state
wineboot duration	completed in 0s	completed in ~30s
kernel32.dll	present=no	present=yes
Prefix arch marker	missing	populated
Socket errors	Function not implemented	no errors

---

Environment from Logs

• Wine version: Wine 11.7 (Staging)
• WINEARCH: win64
• WINEPREFIX: /home/steam/.wine
• WINEDLLOVERRIDES: mscoree,mshtml=
• Container: windrose (ghcr.io/uberdudepl/windrose-dedicated-server-docker:staging)

[Dragon-Slayer32]

ok after adding

services:
windrose:
security_opt:
- seccomp:unconfined

to the docker-compose.yml file it seems like that did it, it is now running
i cant thank you enough for your help @UberDudePL

[UberDudePL]

Awesome! Glad that it works now!

[usoninja]

Option 1 also worked for me, but Option 2 does not as the seccomp/default.json file can't be downloaded (404 error).

[UberDudePL]

@usoninja
https://github.com/moby/profiles/blob/main/seccomp/default.json