After container install, it crashes over and over until I manually stop it.

[frostxinfinity]

Just as stated in the title. I have it installed, proper folders have been created and mapped. I did change the stock ports because this is a secondary dedicated server specifically for mods. They are 25600,25650,25751,25752,8083, and 8084 instead of the original ones. I am not seeing anything in the logs, it's almost as though it just crashes right off the bat and doesn't even have time to write a log output. Anything I can check on concerning this or is the port mapping that is screwing this up? Thanks for your help.

[vinanrra]

Hi, I will try myself the container

[frostxinfinity]

I am running this via Docker on a Synology DS1621+. I just noticed that the Synology DSM software wasn't up to date which may mean Docker isn't up to date. I am doing that right now, will check for Docker updates, and then report back if the issue persists. Thank you.

[vinanrra]

I am running this via Docker on a Synology DS1621+. I just noticed that the Synology DSM software wasn't up to date which may mean Docker isn't up to date. I am doing that right now, will check for Docker updates, and then report back if the issue persists. Thank you.

Hi, I was able to install, startup the server and connect the server, I have also tested to restart the container and connect again, nothing have failed, seems to be a problem on your side.

Which, it's your CPU? Because this container doesn't support ARM

[frostxinfinity]

It has a 2.2Ghz AMD Ryzen V1500B CPU and 32GB of RAM.

[vinanrra]

You should be able to start the server, check configurations maybe something it's wrong.

[frostxinfinity]

Now I am seeing this in the log "crontab: crontabs/sdtdserver: rename: Operation not permitted | stdout". I was not seeing that before, any ideas on that? Thank you.

[vinanrra]

Check folder permission

[Cheef239]

Hey Im having a similar issue where the container gets stuck in an endless boot cycle when verifying installation. Any idea where I should look? Thank you

[vinanrra]

Upload the log folder

[Cheef239]

We got it figured out, for some reason the ports werent mapping correctly.

[frostxinfinity]

How did you fix this, Cheef239? Did you just resort to the original ports?

[Cheef239]

Sorry for the late response! We had to use docker run with all of the specifications instead of docker-compose.