{"version":"2.1.281","anchor":"docker-logs-docker-inspect-read-only-checks-now-refuse-rem","canonical_anchor":"docker-logs-docker-inspect-read-only-checks-now-refuse-rem","heading":"docker logs \/ docker inspect read-only checks now refuse remote-daemon flags and tilde paths","tier":"notice","area":"Bash Safety","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/docker-logs-docker-inspect-read-only-checks-now-refuse-rem","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### docker logs \/ docker inspect read-only checks now refuse remote-daemon flags and tilde paths\n\n`docker logs` and `docker inspect` stop running automatically as read-only when given connection flags or tilde paths\n\n**What**\n\nClaude Code treats `docker logs` and `docker inspect` as read-only commands it can run without asking. Both now use a stricter check, and a command is no longer approved automatically when it includes:\n\n- An option that picks which Docker daemon or connection to use, from a list including `--host`, `--context`, `--config`, `--tlscacert`, `--url`, `--connection`, `--identity`, `--remote` and `--out`\n\n- Such an option hidden inside bundled short flags, such as `-Hx`\n\n- A `~` after `=` or `:`\n\n- A `~` together with `{`\n\nA Docker daemon is the background service that actually carries out docker commands, and it may be on another machine. In a shell, `~` can expand into a home directory path.\n\n**Why**\n\nA docker command that looks harmless can be pointed at a different machine or path by these options. Such commands now show a permission prompt instead of running silently.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}