Venice unleashed linux dedicated server running inside Docker

Hi, thanks for the container, I get this error

[image]

any idea?

what version of wine did you use?

Did you check permissions to files?

unRaid runs things as 99:100 , user: group, respectively.
You need to change that in the entrypoint.sh.

Hi All, having a bit of trouble getting this going.

Ubuntu 22.04 via Proxmox 8.2 (Proxmox VE Helper-Scripts) on a Minisforum MS-01.

I can deploy the container using ‘compose’ or ‘run’ suggested in the original post (or ‘create’ below), same outcome:

docker create \
--name veniceunleashed \
--restart unless-stopped \
-p 47200:47200/tcp \
-p 7948:7948/udp \
-p 25200:25200/udp \
-e O_EMAIL='[email protected]' \
-e O_PASSWORD='myPa55w0rd' \
-e LISTEN='0.0.0.0:25200' \
-e HARMONYPORT='7948' \
-e RCONPORT='0.0.0.0:47200' \
-v /home/docker/veniceunleashed/bf3/:/vu/bf3 \
-v /home/docker/veniceunleashed/instance/:/vu/instance \
-v /home/docker/veniceunleashed/client/:/vu/client \
itsteckel/vu:latest

Note the corrections to the -e in the original ‘Docker run’ section above to match ‘Docker-compose’ section, fixing the 3x LISTEN to LISTEN, HARMONYPORT & RCONPORT to match their actual environment variable

/home/docker/veniceunleashed/bf3 contains all files from my BF3 install on my windows machine.
/home/docker/veniceunleashed/instance contains a fresh server.key file from Login - VU
/home/docker/veniceunleashed/client…

…when the container starts with empty ‘client’ folder, (step 3 on the first/top/original post) I get this:
/bin/sh: 1: /vu/client/entrypoint.sh: not found
on loop until container stops itself

If I put a copy of entrypoint.sh from the github into the folder, same error.
If I change the permissions on the file to any combination of Read and Write (e.g. 0444 or 0666 etc), I get:
/bin/sh: 1: /vu/client/entrypoint.sh: Permission denied

If I change the permissions on the file to any combination of Read + Write + eXecute (e.g. 0777 etc), I get:
/bin/sh: 1: /vu/client/entrypoint.sh: not found

Doesn’t matter if file(s) or folder(s) are owned by root or other user, same outcome.

Doesn’t matter which user creates the docker container, same outcome.

I can create other docker containers without issue in the /home/docker/containername path, no problems with permissions for configuration files and the like.

I spun up another couple of Ubuntu instances (VM + LXC), no change.

Anyone experienced this before or have any handy hints? Thanks