-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fresh pull using recommended docker cli docker image crashes #43
Comments
I also have problems now for some reason (did not run server for like 6-8 months). Tried with fresh server and persistentdata folders too just to make sure previous things did not mess things up. version: '3.7'
services:
vrising:
container_name: vrising
image: trueosiris/vrising
network_mode: bridge
environment:
- TZ=Europe/Warsaw
- SERVERNAME=Zurkoland
- WORLDNAME=zurkoland
volumes:
- './server:/mnt/vrising/server:rw'
- './persistentdata:/mnt/vrising/persistentdata:rw'
ports:
- '9876:9876/udp'
- '9877:9877/udp'
- '27015:27015/udp'
- '27016:27016/udp'
restart: unless-stopped
stop_grace_period: 2m Server error:
|
I'm facing the same issue, ending with message AppPolicyGetProcessTerminationMethod And nothing else then, and the server is not visible in the list, I can't connect to it directly neither I tried on fresh VM, same issue Here is my log
while this used to work with that docker image, on the very same server before |
Exactly the same error message sadly. If I connect before it I can connect and the game will say "Server starting up x/225" and it will freeze at 112 and give a timeout error. |
for anyone interested. the problem is the wine version. So, the DIY way is to pull the repo from the osiris, build docker and use it inside your docker compose. You can use docker hub to push it but do not rly. Easy way is to just use already updated docker from my dockerhub, which has slight modification to include Wine 8 from winehq. Easy way, just change the image:Modify docker-compose.yml (https://hub.docker.com/repository/docker/mzurkowski/vrising/general)image: trueosiris/vrising -> image: mzurkowski/vrising-on-linux:2023-10-12.1 DIY:git clone https://github.com/TrueOsiris/docker-vrising
cd docker-vrising If you want latest wine version (optional)Remove line 26-27 from Dockerfile
replace with
Modify YOUR_DOCKERHUB/vrising to your own repo/tag, i use date as tagdocker buildx build . --push --tag YOUR_DOCKERHUB/vrising:2023-10-09.1 ; docker buildx build . --push --tag YOUR_DOCKERHUB/vrising:latest```
### Modify docker-compose.yml to include YOUR_DOCKERHUB
```yml
image: trueosiris/vrising -> image: YOUR_DOCKERHUB/vrising The ports and configs should be the same and no need to change them. After that, my server works just fine. |
lol the timing on this reply. Crazy. Thanks! |
I just got an email notification coz you posted and remember i fixed it myself some time ago coz i wanted to play xD |
I’ll try to patch it tomorrow. Thx for all the info
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Michał Żurkowski ***@***.***>
Sent: Saturday, January 6, 2024 7:11:00 PM
To: TrueOsiris/docker-vrising ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [TrueOsiris/docker-vrising] fresh pull using recommended docker cli docker image crashes (Issue #43)
CAUTION - This e-mail originates outside of Dedalus. Be vigilant with content, links and attachments!
lol the timing on this reply. Crazy. Thanks!
I just got an email notification coz you posted and remember i fixed it myself some time ago coz i wanted to play xD
—
Reply to this email directly, view it on GitHub<#43 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7JRX5WZXBORF3WGWYNIKTDYNGHTJAVCNFSM6AAAAAA2DV7WXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZG43TEMBWGI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
@michal-zurkowski I get the same error with your image. I'm gonna try the manual way now. |
ah, i changed some things after one update and moved to different name Manual steps should still work tho version: '3.7'
services:
vrising:
container_name: vrising
image: mzurkowski/vrising-on-linux:2023-10-12.1
environment:
- TZ=Europe/Warsaw
volumes:
- './server:/mnt/vrising/server:rw'
- './persistentdata:/mnt/vrising/persistentdata:rw'
ports:
# Ports to list on Steam
- '9876:9876/udp'
- '9877:9877/udp'
restart: unless-stopped
stop_grace_period: 2m |
nice, thanks |
@michal-zurkowski can't pull that image I think, it gives an error. Also made my own image but I get the same error sadly when starting up the server. correction: After switching from Ubuntu to Debian 12 CLI error is gone and server works fine. Thanks for the help! |
hi! @jozsaVilmos could you please tell what you changed exactly to switch from ubuntu to debian? and the server still produces errors (but different):
some things may have changed since january :( EDIT: seems to work; just very slow to be up :D |
I added an image trueosiris/vrising:winehq |
Upon looking within the mounted volumes, I only see the data/Settings directory get created. Not really sure how to move forward.
Here's my docker run bash script:
The text was updated successfully, but these errors were encountered: