jsknnr
commented
7 months ago Yeah this is lower level than permission on a volume. Which Linux distribution are you using? Is this WSL, a VM, or Linux installed on bare metal?
Closed realdegrees closed 7 months ago
jsknnr
commented
7 months ago Yeah this is lower level than permission on a volume. Which Linux distribution are you using? Is this WSL, a VM, or Linux installed on bare metal?
realdegrees
commented
7 months ago Thanks for the quick response, it's Ubuntu 18.04.6 LTS on a VPS.
jsknnr
commented
7 months ago That may be the issue. Your kernel is quite old "4.15.0-177-generic", and that version of Ubuntu is LTS for 2018. I tested on my Windows machine running WSL Ubuntu 22 which has kernel 5.X and my actual container host which is Debian bare metal running kubernetes has kernel 6.X. Can you try running on a newer release of Ubuntu?
realdegrees
commented
7 months ago Okay ty, will do that and check back later
realdegrees
commented
7 months ago Upgraded to 22.04 and I am getting the same error on my VPS. I tried on my windows machine with WSL2 (which is 18.04.6 btw) and it works fine there. But obviously I need it to run on my VPS. Maybe there are some packages that wine needs that I could be missing? But I thought docker containers were pretty much standalone and don't depend on the host at all.
fleaz
commented
7 months ago Had the same issue on my Debian 10 (Kernel 4.19.0) server. Switched to a different VM with Ubuntu 22.04 (5.15.0) and it works.
So maybe indeed a kernel issue.
crsleeth
commented
7 months ago I'm getting the same issue on Ubuntu 22.04 kernel 5.15.0 (virtual machine)
bebar69
commented
7 months ago I had the same issue with 64bits OS Ubuntu 22.04 (vm on esxi)
madimaa
commented
7 months ago I had the same issue with a VM on my Proxmox VE. I changed the VM's CPU from kvm64 to host and it works now.
jsknnr
commented
7 months ago So this could either be an issue with a kernel that is too old. It should be at least 5.X OR it is an issue with the CPU_FLAGS that are being passed into the VM from the hypervisor being insufficient.
I helped some one fix this issue earlier today by having them switch their cpu type form kvm64 to host to keep all the physical flags in tact.
If you are on kernel 5.X or newer, then your issue is that you need to change the level of emulation from your hypervisor. It works on WSL2 because the CPU is not emulated at all.
crsleeth
commented
7 months ago I had the same issue with a VM on my Proxmox VE. I changed the VM's CPU from
kvm64tohostand it works now.
Yes in Proxmox changing my processor to [host] fixed the issue for me. Great call!
realdegrees
commented
7 months ago So I upgraded my kernel to 6.5.0-14-generic and I'm still getting the error. Since I'm on a VPS I can't really change anything, so my CPU is just unsupported and I'm out of luck I guess? I'm also assuming this has nothing to do with your image but the actual server code correct?
crsleeth
commented
7 months ago My assumption is it is an issue with the .exe and Wine. I also tried hosting without Docker using this script that uses SteamCMD + Wine and ran into the same error (until I changed my VM's CPU architecture to host).
LCzoboriek
commented
7 months ago What issues could arrise if i changed the vms cpu architecture to host? Im having the exact same issue, running on a vm in proxmox
madimaa
commented
7 months ago What issues could arrise if i changed the vms cpu architecture to host? Im having the exact same issue, running on a vm in proxmox
You can't live migrate to another server.
pipos666
commented
7 months ago Same issue here, running Debian in a physical machine: Debian 6.1.69-1 (2023-12-30) x86_64.
LCzoboriek
commented
7 months ago Fixed the issue by making the cpu architecture as host, not too fussed about migrating to another server so thats all good
jsknnr
commented
7 months ago So this is not an issue with this image as I have seen reports of this same error from other images. This is a tricky issue. I have helped a few folks debug this and in each case the cause is either the Kernel is too old or there is an issue with the CPU missing the required flags.
zistil
commented
7 months ago I was getting the same error. I am running a ubuntu 22.04 with 6.x kernel virtualized with kvm (proxmox). Tried bunch of different CPU type etc. What worked for me is running the container as privileged by adding 'privileged: true' to the docker-compose.yaml file. Probably not best practice but it did do the trick.
realdegrees
commented
7 months ago I just tried launching it again today out of curiosity and it works now. No changes, so I guess they updated their servercode 👍
bebar69
commented
7 months ago Error fixed with patch hotfix 3 ... CPUs that do not support AVX should now be able to host sessions ....
KayTaneJupiter
commented
6 months ago CPUs that do not support AVX should now be able to host sessions ....
Exactly what is the minimum CPU? (And why is it so high?)
I have a PCs which can run a dedicated server for Valheim all day and night but Enshrouded crashes.
fleaz
commented
6 months ago Exactly what is the minimum CPU? (And why is it so high?)
I have a PCs which can run a dedicated server for Valheim all day and night but Enshrouded crashes.
AVX has been supported in CPUs since ~2011 https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX
KayTaneJupiter
commented
6 months ago Exactly what is the minimum CPU? (And why is it so high?) I have a PCs which can run a dedicated server for Valheim all day and night but Enshrouded crashes.
AVX has been supported in CPUs since ~2011 https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX
So what?
fleaz
commented
6 months ago So what?
You were complaining about a "too high requirement for a recent CPU", which is imho not really valid for feature that is roughly 13 years old.
KayTaneJupiter
commented
6 months ago You were complaining about a "too high requirement for a recent CPU", which is imho not really valid for feature that is roughly 13 years old.
Thanks for your "opinion".
Could you go away now? Adults are talking.
I am using docker-compose to launch the image and it crashes on startup with the same error every time. I'm using the default docker-compose you provided with the default .env values too. I tried to change the permissions of the volumes as well but that doesn't seem to change anything.
Any idea what the issue could be? Thank you for providing this image!