# 19 October: Docker API filter, tighter container egress, Retry-After on rate limits 2026-10-19 · Security > The Docker API on the host sits behind a filter, outgoing traffic from the default Docker bridge is restricted, and rate-limited pairing endpoints say when to retry. Added on 23 October 2026 from the repository history. Wording follows commit subjects. *Outbound traffic from a workspace. Diagram from the docs.* Text version Traffic from a workspace leaves through a filtered path. Everything not on the allowed list is dropped and counted. ## Security - The Docker API is reached through a filter in its own network. The app account no longer holds the Docker key, and docker inspect hides environment values. - Outgoing traffic from the default Docker bridge is limited to the worker nodes' remote-desktop ports. Everything else is dropped and counted. - The firewall helper accepts a fixed list of commands instead of general sudo iptables. - Device claim, pairing, extension redeem and provider-key endpoints send a Retry-After header with 429 responses. Correction to the entry about per-account memory encryption (dated 20 October): the encryption code went live on 19 October at 17:17 UTC.