tshock-latest via compose starts vanilla Terraria server

[CTOUT]

Hi,

It's entirely possible it's something I've done (or don't understand!) as I'm relatively new to Docker. However, when starting the tshock-latest tag with a compose file I only seem to get a vanilla Terraria server instance running.

When I run the docker CLI command to start the same image, I get tShock.

CLI command: docker run -it --name=terraria -p 7777:7777 beardedio/terraria:tshock-latest

Compose file contents: -

`version: "3.9"

services: tShock: image: beardedio/terraria:tshock-latest ports:

• "7777:7777" restart: unless-stopped environment:
• world=Map.wld volumes:
• /tShock/config:/config
• /tShock/plugins:/tshock/ServerPlugins tty: true stdin_open: true`

When attaching to the instances and running mono TerrariaServer.exe you can see the difference in the output: -

CLI: -

`mono TerrariaServer.exe Error Logging Enabled. TerrariaAPI Version: 2.1.0.0 (Protocol v1.4.2.3 (238), OTAPI 1.4.2.3) TShock 4.5.4.0 (Blood Moon edition) now running. AutoSave Enabled Backups Disabled Welcome to TShock for Terraria! TShock comes with no warranty & is free software. You can modify & distribute it under the terms of the GNU GPLv3. [Server API] Info Plugin TShock v4.5.4.0 (by The TShock Team) initiated. Terraria Server v1.4.2.3

n New World d Delete World

Choose World: `

Compose: -

`mono TerrariaServer.exe Error Logging Enabled. TerrariaAPI Version: 2.1.0.0 (Protocol v1.4.2.3 (238), OTAPI 1.4.2.3) Terraria Server v1.4.2.3

n New World d Delete World

Choose World: `

[CTOUT]

ok, compose seems to work as expected if I don't mount the config path.

[CTOUT]

Nevermind, looks like something spurious was happening with the mounting of the plugins directory, and as a result the DLL file that goes in there was misplaced and didn't load the "tshock" side of things.