mwessman
commented
9 months ago Here is my docker-compose.yml file. I simply renamed the docker-compose-proton.yml to the default name and made some changes to the env variables:
version: "3.8"
services:
enshrouded:
build:
context: .
dockerfile: dockerfiles/proton.Dockerfile
args:
WINE_BRANCH: stable
image: mornedhels/enshrouded-server:dev-proton
container_name: enshrouded
hostname: enshrouded
restart: unless-stopped
stop_grace_period: 90s
ports:
- "15636-15637:15636-15637/udp"
volumes:
- ./game:/opt/enshrouded
environment:
- SERVER_NAME=***
- PUID=4711
- PGID=4711
- SERVER_PASSWORD=***
cp-fabian-pittroff
Is there an existing issue for this?
Used image version
dev-proton
Used docker compose file or docker command
docker-compose-proton.yml
What you expected to see, versus what you actually saw
I expected to get a normal build going like with the wine version, but with Proton it doesn't work. I pasted the logs below, and I believe the main problem is this part:
2024-01-28 09:01:00.575 supervisord: enshrouded-updater Error! App '2278520' state is 0x202 after update job.I looked through some other issue threads and found that you mentioned a force update:
docker compose exec enshrouded supervisorctl start enshrouded-force-updateBut that didn't help either.The reason I want to use Proton is because the wine server lags like crazy, and from what I've heard, using Proton makes it a lot smoother.
Logs from the container