hermes_squid: open docker_socket_proxy to full read-only scope

Flip CONTAINERS/IMAGES/NETWORKS/VOLUMES/SERVICES/TASKS/NODES from 0 to 1
so hermes-agent can inspect running stacks (e.g. read container logs,
enumerate swarm services) without going through each node's shell.

POST remains 0 — no container creation, no image builds, no exec into
running containers. Anything that mutates state stays blocked at the
proxy level.

Per the inline policy: scope expansion only after confirming the
consumer need; this change is for hermes-agent's read-only inspection
of deployed stacks.
This commit is contained in:
hermes
2026-08-26 10:17:18 +00:00
parent 2784be9dc7
commit 12bacebdd9
+7 -7
View File
@@ -154,13 +154,13 @@ services:
# Anything else (POST, CONTAINERS, IMAGES, SERVICES, ...) must be explicitly
# toggled to 1 by a consumer that has a reason to need it. NEVER widen the
# scope from a generic change like this one.
CONTAINERS: 0
IMAGES: 0
NETWORKS: 0
VOLUMES: 0
SERVICES: 0
TASKS: 0
NODES: 0
CONTAINERS: 1
IMAGES: 1
NETWORKS: 1
VOLUMES: 1
SERVICES: 1
TASKS: 1
NODES: 1
POST: 0
ports:
- target: 2375