···11111212Combined with a socket-proxy container that provides granular endpoint access it's possible to expose only information about specific containers in a read-only context.
13131414+## Features
1515+1616+### `CONTAINER_NAMES`
1717+1818+Using this ENV changes Docker API responses:
1919+2020+* Filters [List Containers](https://docs.docker.com/reference/api/engine/version/v1.48/#tag/Container/operation/ContainerList) responses so any container with a name that does not include a value from `CONTAINER_NAMES` is removed.
2121+* Any other [Container](https://docs.docker.com/reference/api/engine/version/v1.48/#tag/Container) endpoints will return 404 if the container name does not include a value from `CONTAINER_NAMES`
2222+2323+### `SCRUB_ENVS`
2424+2525+When `true` any responses from the [Container Inspect](https://docs.docker.com/reference/api/engine/version/v1.48/#tag/Container/operation/ContainerInspect) endpoint will have `Config.Env` set to an empty array.
2626+1427## Example
15281629```yaml