CurseForge server no longer starting.

[scottmando2000]

Describe the problem

Since the update 2 days ago, my All The Mods 7 CurseForge server will no longer start properly.

Container definition

version: "3"

services:
  atm7:
    image: itzg/minecraft-server
    environment:
      EULA: "TRUE"
      ENABLE_RCON: "FALSE"
      TYPE: "CURSEFORGE"
      PAPERBUILD: 318
      MEMORY: 16G
      SPAWN_PROTECTION: 0
      UID: 1234
      GID: 1234
      CF_SERVER_MOD: "/modpacks/SIMPLE-SERVER-FILES-0.3.20.zip"
    tty: true
    stdin_open: true
    restart: unless-stopped
    user: 1234:1234
    volumes:
      - ./atm7:/data
      - ./modpacks:/modpacks

Container logs

minecraft-atm7-1  | [init] Looking for Feed-The-Beast / CurseForge server modpack.
minecraft-atm7-1  | [init] Conflicting FTB/CurseForge packages have been installed. Please cleanup /data/FeedTheBeast
minecraft-atm7-1  | [init] Running as uid=1234 gid=1234 with /data as 'drwxrwxr-x 3 1234 1234 4096 May  6 00:38 /data'
minecraft-atm7-1  | [init] Resolved version given LATEST into 1.18.2 and major version 1.18

[itzg]

Did you try what it requested

minecraft-atm7-1  | [init] Conflicting FTB/CurseForge packages have been installed. Please cleanup /data/FeedTheBeast

[scottmando2000]

Did you try what it requested

minecraft-atm7-1  | [init] Conflicting FTB/CurseForge packages have been installed. Please cleanup /data/FeedTheBeast

Why exactly should I be removing the data directory for the server? This issue started happening after the watchtower pulled the latest version of the available docker image, and has been working perfectly fine beforehand, including restarts.

[itzg]

This is a regression introduced by #1534 . I'm working on a tighter discovery mechanism.

[itzg]

The latest image should now fix this.

...however, I also want to fix the thing where modpacks like this that use ServerStarter with a setup subdirectory correctly apply the EULA file.