Profile [env.*] cannot override LOCALSTACK_HOST (launcher value appended last)

環境変数の組み立てを行う266～296行付近の internal/container/start.go から始め、SF_S3_ENDPOINT のガードと MAIN_CONTAINER_NAME の警告を、LOCALSTACK_HOST の追加方法と比較してください。コンテナ環境の構築に関する近くのテストを確認し、プロファイルから指定された LOCALSTACK_HOST のカバレッジを追加してください。完了条件は、プロファイルの値が反映されるか、無視されることを明確に説明する警告が出ること、そして選択した動作がテストされていることです。

Observed

Setting LOCALSTACK_HOST in a config [env.*] profile has no effect. The container receives the variable twice — the profile value first, lstk's computed value second — and Docker's last-wins semantics keep lstk's. docker inspect on a type = "snowflake" container started with a profile containing LOCALSTACK_HOST = "sf.example.test:4599" shows both entries; the emulator sees localhost.localstack.cloud:4599. Nothing warns that the profile value was dropped.

Where

internal/container/start.go on main (d9c83037):

• :276 env := resolvedEnv — the profile's variables come first;
• :281-285 env = append(env, "GATEWAY_LISTEN=…", "MAIN_CONTAINER_NAME=…", "LOCALSTACK_HOST="+endpoint.Hostname+":"+c.Port) — lstk's own value is appended unconditionally after them.

The two neighbours already handle this collision: SF_S3_ENDPOINT (:292) is appended only when the profile did not set it (!envHasKey(resolvedEnv, "SF_S3_ENDPOINT")), and MAIN_CONTAINER_NAME (:266-275) emits a warning saying the profile value is ignored. LOCALSTACK_HOST does neither, so the profile value vanishes silently. (A LOCALSTACK_HOST exported in the host shell does win, because hostEnv is appended at :296 after lstk's line — so the two configuration channels behave differently.)

Context

Recorded in September 2026 while diagnosing a snowflake-next result-chunk 404 under lstk (the emulator advertised the host lstk injected but its hostname gate did not route it; that was fixed on the emulator side, which now routes any host it is told to advertise). For the default flow this is harmless: the value lstk injects, localhost.localstack.cloud:<published port>, is the right one. It only matters when a user needs a different advertised host — a non-loopback hostname for clients on other machines, or a reverse-proxy name — and reaches for the documented [env.*] mechanism to set it.

Expected

Either the profile wins — append lstk's LOCALSTACK_HOST only when the profile did not set it, with the same envHasKey guard SF_S3_ENDPOINT uses — or lstk warns that the profile value is ignored, as it does for MAIN_CONTAINER_NAME, and the config docs state that LOCALSTACK_HOST is launcher-owned.

Reproduce

[[containers]]
type = "snowflake"
port = "4599"
env = ["custom"]

[env.custom]
LOCALSTACK_HOST = "sf.example.test:4599"

lstk start, then docker inspect <container> --format '{{json .Config.Env}}' → both LOCALSTACK_HOST=sf.example.test:4599 and LOCALSTACK_HOST=localhost.localstack.cloud:4599, in that order; inside the container echo $LOCALSTACK_HOST prints the latter.