Plugins not loading

[asumaray]

I've added some plugins and restarted the server, but the plugins are not being recognized. I've validated that the plugins exist in the host directory, but when I actually exec'd into the container and checked the ServerPlugins folder it did not appear that my plugins were copied over.

Relevant portion of my docker-compose:

terraria:
    container_name: terraria
    image: ryshe/terraria:latest
    stdin_open: true # docker run -i
    tty: true # docker run -t
    environment:
      - WORLD_FILENAME=2024.wld
    ports:
      - 7777:7777
    volumes:
      - /mediaserver/terraria/world:/root/.local/share/Terraria/Worlds
      - /mediaserver/terraria/ServerPlugins:/plugins
    restart: unless-stopped

[SirMonkeyBoy]

I don't think that's running TShock with is what I'm guessing your trying to use you need to use the image
ryshe/terraria:tshock-latest

[asumaray]

I was under the impression that it was the opposite and I would have to explicitly specify vanilla. I attached to the container and did /version and it appears to be Tshock:

[SirMonkeyBoy]

Ok I've just used the tshock image but if that's tshock then I'm not sure can you send your console logs

[JoseFcoRosado]

right bind to plugins is:
<your_path>:/tshock/ServerPlugins

[Zsongli]

right bind to plugins is: <your_path>:/tshock/ServerPlugins

Thank you, I had the exact same problem and this fix works, but the on Docker page it says:

Mount the plugins directory with an additional -v switch on your docker run ... command
-v <path_to_your_ServerPlugins_folder>:/plugins

So I suggest you update the page in order to avoid any misunderstanding in the future.

[caporalesimone]

I think that on latest version, the mistake is in the bootstrap script

# Copy plugins if the folder is empty (like on first run)
if [ -z "$(ls -A /tshock/ServerPlugins)" ]; then
  echo "Copying plugins..."
  cp /plugins/* /tshock/ServerPlugins
fi

Seems that folder /tshock/ServerPlugins contains already something and the check fails skipping the copy.

[kpureblade]

Wanted to add a bit of my findings on this, I'm a docker newb so still learning, but think I understand what is happening somewhat. The docker container presented here on its own already has a few plugins/files in the ServerPlugins directory, TShockAPI.deps.json, TSHOCKAPI.dll, TSHOCKAPI.pdb, and TShockAPI.xml. If you use JoseFcoRosado's suggestion above and rebind the volume over the /tshock/ServerPlugins directory, those files get covered up, and I think that essentially disables TShock. I got around this by taking those four files and placing them in my plugins folder outside the container, so now when the container starts it has all of those files plus the additional plugin(s) I want. What caporalesimone says makes sense to me, that some code isn't working to merge the contents of /plugins with /tshock/ServerPlugins. That's about the extent of my knowledge on this though!

And I wanted to add as a side note, I found this project through dockerhub, and there is a link on that page to MicroBadger at the top. That link appears to lead to a malicious website and should most likely be removed.

[ryansheehan]

I got behind on maintaining issues here. MicroBadger has been removed. Thanks for all the community support.