docs(lstk hotfix): update CLI reference to v0.20.1

[gtsiolis]

Brings the lstk CLI reference docs up to date with the v0.20.1 release of localstack/lstk, catching up from the last-documented v0.19.0 (the full v0.19.0 → v0.20.1 range).

Reference pages in scope

• src/content/docs/aws/developer-tools/running-localstack/lstk.mdx
• src/content/docs/azure/developer-tools/lstk.mdx

There are no shared lstk components yet, so each page is edited directly and kept in sync.

What changed since v0.19.0

Container runtime auto-detection (localstack/lstk#399)

• Reworked the runtime-discovery note: lstk supports Docker Desktop, Rancher Desktop, Colima, OrbStack, Lima, and Podman, resolving in order via DOCKER_HOST → DOCKER_CONTEXT/current Docker CLI context → per-runtime socket probe → Docker SDK default, with a start-command hint tailored to the detected runtime on failure. Replaces the old Colima/OrbStack-only sentence.
• Updated the "Docker is not running" troubleshooting fix to name the full runtime set and the tailored start-command hint.
• Rewrote "Port 443 already in use": with the default GATEWAY_LISTEN, a busy or unbindable port 443 is no longer fatal — lstk drops it with a warning and serves HTTPS on the edge port 4566; a port listed explicitly in GATEWAY_LISTEN stays a hard requirement. The old daemon hard-failure snippet no longer represents the default path, so it was removed.

Runtime endpoint precedence on Linux (localstack/lstk#422)

• Noted that on Linux a running Docker daemon is preferred over a co-installed runtime such as Podman when resolving the container endpoint.

Logs streaming (localstack/lstk#418)

• Noted that interactive lstk logs writes lines to the terminal's scrollback, so full history is preserved (like docker logs).

Accuracy fix noticed on the way

• The Azure page's "Port 443" config example used type = "aws"; corrected to type = "azure".

No doc change required

• lstk aws streaming commands (e.g. aws logs tail --follow) no longer buffer their output until exit (Fix lstk aws streaming output hanging until exit by running the aws CLI in a PTY lstk#417). This is a bug fix restoring expected behavior; the reference docs never described the buffering, so no wording changed.

Review

Recommend a quick human read of the public-facing wording in the rewritten "Port 443 already in use" section (the drop-with-warning framing). The rest is a straightforward reference-doc sync.

Closes DOC-381

Cc @localstack/devx for visibility and any corrections.

[cloudflare-workers-and-pages]

Deploying localstack-docs with    Cloudflare Pages

Latest commit:	6d80032
Status:	✅  Deploy successful!
Preview URL:	https://9f29bdb5.localstack-docs.pages.dev
Branch Preview URL:	https://claude-affectionate-edison-v.localstack-docs.pages.dev

View logs

[gtsiolis]

The red Validate Refs check is the Restrict Docs PR merges policy gate, which rejects any PR to main whose head branch isn't aws-docs-* / snowflake-docs-*. It's not caused by this diff — it fails the same way on every docs PR from a normal branch (including the prior lstk sync #830, which merged cleanly). The actual build and link validation passed: the Cloudflare Pages preview deployed successfully.

---

Generated by Claude Code