As described in issue #28, this users of this container have been experiencing several issues with getting the server to start and load mods properly. To solve this, I have rolled back the security changes made back as a suggestion from #12. To those concerned with container security, I reviewed several containers hosting game servers, and it seems like this configuration is common place. With that in mind, I made the necessary changes to support the maximum number of users with varying Docker implementations.
In addition, I have taken the time to update the file directory structure to use a common /data directory. Mapping this directory to your host through the volumes compose configuration, or with the -v flag will preserve the downloaded workshop mods, and world files. This means that previous configurations will break, and users should update their environment variables to reflect.
This change in directory mapping has been communicated within the start script of the container to help ease you into the adjustment.
Next, due to the impending tModLoader 1.4.4 release, I have placed a couple notices alerting of the high probability of this update breaking this container. Users should keep an eye on the Github repo for updates posted on top of the README and on the issues page as well for how to proceed.
Finally, there is a discord now! For those who want to chat or ask for support on configuring the container, please feel free to join!
As described in issue #28, this users of this container have been experiencing several issues with getting the server to start and load mods properly. To solve this, I have rolled back the security changes made back as a suggestion from #12. To those concerned with container security, I reviewed several containers hosting game servers, and it seems like this configuration is common place. With that in mind, I made the necessary changes to support the maximum number of users with varying Docker implementations.
In addition, I have taken the time to update the file directory structure to use a common /data directory. Mapping this directory to your host through the volumes compose configuration, or with the -v flag will preserve the downloaded workshop mods, and world files. This means that previous configurations will break, and users should update their environment variables to reflect.
This change in directory mapping has been communicated within the start script of the container to help ease you into the adjustment.
Next, due to the impending tModLoader 1.4.4 release, I have placed a couple notices alerting of the high probability of this update breaking this container. Users should keep an eye on the Github repo for updates posted on top of the README and on the issues page as well for how to proceed.
Finally, there is a discord now! For those who want to chat or ask for support on configuring the container, please feel free to join!