[BUG] Docker control plane: first-run setup friction (config carry-over, port collision, DB defaults)

[Icehunter]

Splitting these out of #311 so they do not get lost in that thread. All three came from @wofnull testing a control: docker install against the redblinks dune-docker stack, quoted verbatim below.

1. Existing ~/.dune-admin/ blocks setup carrying over to a new binary

i deleted the old .dune-admin folder in userfiles, as it hindered the -setup to carry over with the new excutable

Dropping a new binary next to an existing config should either reuse that config or let -setup overwrite it. Having to delete the whole directory to get setup to work is not an acceptable upgrade path, and it costs the operator their server registry and dashboard password too.

Needs reproducing: run -setup against a ~/.dune-admin/ written by an older version and find what specifically refuses to carry over. needsSetup() reads the servers store first and falls back to a flat-config heuristic (main.go:745), so the store and config.yaml disagreeing is a likely suspect.

2. Listen port collides with dune-docker, and 18080 is rejected

if dune-docker is started WITHOUT any setup it starts on port 18080, web setup is missing the new "setup steps"
if dune docker is started WITH setup parameter it sets up on port 8080. If manually set to 18080, the dune-docker start, denies starting up with error "Port not set in config"

Two things here.

The :18080 fallback in the wizard is gated on ctrl == "amp" (setup.go:87), because AMP's own panel takes 8080. dune-docker appears to have the same collision, so the docker control plane likely wants the same treatment, or a port probe.

"Port not set in config" does not appear anywhere in this repo, so that error is coming from the dune-docker stack rather than from us. @wofnull, could you confirm which process printed it and paste the surrounding output? That decides whether this is our bug or a config-shape mismatch with theirs.

3. Preset the dune-docker postgres defaults

base password for the postgres installation is dune and can be userchanged if needed, its locked to local access via 127.0.0.1 only, connection via other IPs does not work ( dune-docker based setting ) ( therefore PW and host can be preset )

runDockerSetup currently prompts for DB host with a default of database and asks for the password with no default. For a stock dune-docker install the answers are known: host 127.0.0.1, user dune, password dune. Offering those as defaults would remove two guesses from the flow.

Worth confirming they are stable across dune-docker versions before hardcoding them, since a wrong default is worse than no default here.

Scope

1 and 2 are bugs. 3 is a setup-flow improvement. They are grouped because they are all first-run friction on the same install type, but they can be split if that is easier to work.

Reported by @wofnull in #311.

[wofnull]

For the 2nd part, the dune-docker interface does NOT block 8080 or 18080, it uses as only not common port 8088 for its own webinterface.

for the port not found part, here the complete log from the setup session, defining port 18080, and the error from the dune-admin startup missing port in address , signing off with error: "listen tcp: address 18080: missing port in address"

wofnull@dunebuntudocker:/opt/dune-admin$ ./dune-admin -setup

=== dune-admin setup ===

Control plane:
  kubectl — Kubernetes (k3s) via SSH (current default)
  docker  — Docker containers (docker CLI with named containers)
  local   — Generic local (configurable shell commands)
  amp     — CubeCoders AMP with podman game-server container

  Control plane [kubectl]: docker

Containers found:
    [1] dune-server-deepdesert-1-8       running
    [2] dune-server-sh-harkovillage-4    running
    [3] dune-server-sh-arrakeen-3        running
    [4] dune-autoscaler                  running
    [5] dune-server-gateway              running
    [6] dune-server-survival-1-31        running
    [7] dune-server-overmap              running
    [8] dune-server-survival-1           running
    [9] dune-director                    running
    [10] dune-text-router                 running
    [11] dune-rmq-game                    running
    [12] dune-rmq-admin                   running
    [13] dune-postgres                    running
    [14] redblink-dune-docker-console     running
    [15] dune-public-probe                running
    [16] dune-orchestrator                running
    [17] silly_pasteur                    exited
    [18] portainer_agent                  running

  Auto-detected game servers: dune-server-deepdesert-1-8, dune-server-sh-harkovillage-4, dune-server-sh-arrakeen-3, dune-server-survival-1-31, dune-server-overmap, dune-server-survival-1
  Which containers are game servers? (comma-separated numbers) [1,2,3,6,7,8]:
  ✓ Game servers: dune-server-deepdesert-1-8, dune-server-sh-harkovillage-4, dune-server-sh-arrakeen-3, dune-server-survival-1-31, dune-server-overmap, dune-server-survival-1
  mq-game broker container name (optional) [dune-rmq-game]:
  mq-admin broker container name (optional) [dune-rmq-admin]:
  Battlegroup Director URL (optional) [http://127.0.0.1:11717]:

Database connection:
  DB host (Docker DNS or IP) [database]: 127.0.0.1
  DB port [15432] [15432]:
  DB user [dune]:
  DB password: dune
  DB name [dune]:
  DB schema [dune]:

Connecting to database...
  ✓ Database connected as: dune

Embedded market bot:
  Enable embedded market bot [yes/no] [yes]: no
  ✓ Embedded market bot disabled
  Remote bot URL (leave blank to skip):

Server config:
  HTTP listen address [:8080]: 18080

── Discord Bot (optional) ──────────────────────────────────────────────
Each dune-admin instance uses its own Discord application (bring-your-own-bot).
Create one at https://discord.com/developers/applications, copy the Bot token,
then invite the bot to your guild with the 'applications.commands' scope.

  Enable Discord bot? (y/n) [n]:
  ✓ Discord bot disabled

── Live Events Engine (optional) ───────────────────────────────────────────
  Enable live events engine? (y/n) [n]:
  ✓ Live events engine disabled

  ✓ Config written to /home/wofnull/.dune-admin/config.yaml

Setup complete.

  Run: dune-admin

wofnull@dunebuntudocker:/opt/dune-admin$ ./dune-admin
07:10:27 INF pre-migration backup written component=store path=/home/wofnull/.dune-admin/config.yaml.pre-migrate.bak
07:10:27 INF seeded DB from config.yaml component=config_import server_count=1
07:10:27 INF discord_user_links: migrated legacy registrations component=store count=1
07:10:29 INF catalog seeded component=battlepass tier_count=188
07:10:29 INF proxying /director/ component=server director_url=http://127.0.0.1:11717
07:10:29 INF serving frontend from embedded assets component=server
07:10:29 INF dune-admin listening addr=18080 component=server
listen tcp: address 18080: missing port in address

However seeing this error now, I found that the ":" was missing in my re-setup. I assumed that the : gets added from the setup itself and the port only should contain the portnumber itself, like the way its is done on ohter occassions like the db port, which does not need the ":" specified.
Resetup via console works with port 18080 IF it is entered :18080

For 3rd, its confirmed that the base passwort is dune everytime since start of the dune-docker project. as part of the security hardening, PGSQL is configured only to answer to localhost / 127.0.0.1 requests, therefore a "base" passsword is used. Thus the ability to change the password to anything else in dune-docker webUI.

( screen from dune-docker database info: )

[Icehunter]

Fixed in #327, merged. Bare port ("18080") now gets a colon prepended before it reaches net.Listen, and the docker DB password prompt defaults to dune. Both are confirmable defaults, not silent — you'll still see them and can type over them.

The port collision item wasn't real (dune-docker uses 8088), so nothing needed there.