[nealrichardson]

Fixes #40.

Problem

with-connect tells that Connect has started by reading the container's output for Starting HTTP server on. That message is an INFO-level line in Connect's service log. If a --config file sends [Logging] ServiceLog to a file, or sets ServiceLogLevel to WARN or ERROR, the message never reaches the container output and with-connect fails with "Posit Connect did not log HTTP server start within 60 seconds."

Fix

The container environment includes CONNECT_LOGGING_SERVICELOG=STDOUT and CONNECT_LOGGING_SERVICELOGLEVEL=INFO. Connect gives CONNECT_* environment variables precedence over the config file. The env setup moved into a small build_container_env() helper so it can be tested directly; user -e vars are still applied last, so they can override these defaults.

ServiceLogFormat = JSON does not need handling: the JSON lines still contain Starting HTTP server on [::]:3939 and Starting Posit Connect v..., so the existing substring checks match.

README documents the forced settings next to the CONNECT_ env var paragraph.

Verification with real containers

Used README.md as a stand-in license: Connect starts and logs, then with-connect stops at the license check, which comes after the point where the HTTP server line is logged.

Image	Config	Without fix	With fix
ghcr.io/posit-dev/connect:latest (2026.10.0)	ServiceLog = <file>	"did not log HTTP server start within 60 seconds", only "Using file ... to store Server Logs." in output	Starting HTTP server on [::]:3939 logged, fails on license as expected
ghcr.io/posit-dev/connect:latest	ServiceLogLevel = WARN	No Starting HTTP server line in output (only the license warning, so a valid license would time out)	— (covered by the combined config below)
ghcr.io/posit-dev/connect:latest	ServiceLogFormat = JSON	{"level":"info","msg":"Starting HTTP server on [::]:3939",...} matches	—
ghcr.io/posit-dev/connect:latest	file + JSON + WARN	—	JSON Starting HTTP server on line logged
rstudio/rstudio-connect:jammy-2025.10.0	file + JSON + WARN	—	JSON Starting HTTP server on line logged
ghcr.io/posit-dev/connect:latest	JSON config, -e CONNECT_LOGGING_SERVICELOG=/tmp/x.log	—	User override wins: "Using file /tmp/x.log", times out as expected

A side note from testing: a --config file replaces the image's default rstudio-connect.gcfg entirely, so it also has to set [HTTP] Listen = :3939 (otherwise Connect exits with "No server listeners are configured"). That's outside this fix.

Tests

• test_container_env_forces_service_log_to_stdout: the bootstrap and logging defaults are present.
• test_container_env_user_vars_override_defaults: -e values override the defaults, values containing = are kept, and entries without = are ignored.

Both are registered in the __main__ block. uv run test_main.py and pytest pass.

Merge conflicts with open PRs

git merge-tree against fix-command-errors (#69), clean-errors (#70), and fast-stop (#71) reports no conflicts. There was no #72 or auto-port branch to check.

🤖 Generated with Claude Code