Closed Jan-NiklasB closed 5 months ago
hey, mind trying with the 1.6.1 args? i included those in the latest readme
you can open any ports, if you want to open 6971 and 6972 too, use the run command like this:
docker run --pull=never -v $PWD/server:/opt/server -p 6969:6969 -p 6970:6970 -p 6971:6971 -p 6972:6972 -it --name sitcoop sitcoop
hey, mind trying with the 1.6.1 args? i included those in the latest readme
you can open any ports, if you want to open 6971 and 6972 too, use the run command like this:
docker run --pull=never -v $PWD/server:/opt/server -p 6969:6969 -p 6970:6970 -p 6971:6971 -p 6972:6972 -it --name sitcoop sitcoop
Hey, thanks for the response. I will try it.
I tried already the -p parameter to open more ports, but that shifted, for whatever reason, the default com-ports to these, without any changes to the config files.
I will comeback here to report if this worked for me.
Hey, I tried to reach out on you on Discord but sadly you require phone validation, but I'm not going to share my number with Discord... anyways.
I tried to setup this docker image on a Debian root server running Docker and Portainer. The build process already showed up tons of deprecation messages, but since I see this quite often that's may not be the problem. When running the container after first startup and config it errors with the message:
using
lsof -i :6969
in the container and on the host I found the container itself using this port already and on the host only the container using it when running.So it seems to me that there's something wrong with the image under Linux, since using the same version of this repo under Win10 gives me less build steps and runs fine.
Another SIDE NOTE: since I'm not sure if I missed something, is there an option to tell the container which ports to use for new matches? Since the log tells me that the match is running on port 6972, but that isn't feed to the host and therefor in my test I can't connect to it while normal login works.
Any help would be really appreciated. Thanks Jan-Niklas