fix: make Guacamole fixture dual-stack and keep VM display awake
This commit is contained in:
@@ -208,6 +208,9 @@ Interactive browser access is a deliberately temporary recovery path only. See
|
||||
[`test/rdp-access`](../test/rdp-access/README.md) for the Docker-only,
|
||||
self-signed HTTPS Guacamole lifecycle; it must be started only after the native
|
||||
fixture controller has prepared and leased the VM, and stopped before reset.
|
||||
For a public hostname with an AAAA record, its `up --bind 0.0.0.0` mode also
|
||||
tracks an IPv6-to-IPv4 forward; verify `ipv6_forward=active` before debugging
|
||||
a browser stuck at “Waiting for response”.
|
||||
|
||||
The Linux production Compose asset has a separate, loopback-only smoke lane. It
|
||||
uses a disposable self-signed key only under the ignored `.test-runs` tree,
|
||||
|
||||
Reference in New Issue
Block a user