# Container Scanner

Similarly to the Dockerized Client, the [Container Scanner](https://docs.meterian.io/containers-support/container-scanner) needs to be manually configured to ensure the scan runs for you dedicated instance. Prior to invocation ensure you set the following environment variables as such

<table><thead><tr><th width="225">Name</th><th>Description</th></tr></thead><tbody><tr><td>METERIAN_ENV</td><td>Set this variable to target the right subdomain of the site where your instance runs</td></tr><tr><td>METERIAN_PROTO</td><td>Set this variable to target the right HTTP protocol of the site where your instance runs</td></tr><tr><td>METERIAN_DOMAIN</td><td>Set this variable to target the right domain of the site where your instance runs</td></tr></tbody></table>

You can check that your client is correctly connecting to the dedicated instance executing the client with "--help", which will display the instance and the account it is connecting to.

```
$ export METERIAN_ENV=acme
$ export METERIAN_DOMAIN=meterian.uk
$ docker-scan --help

Meterian Docker Scanner v1.1.9, build a726d16-363

usage: [command] DOCKER_IMAGE_NAME [OPTIONS] i.e.
./docker-scan.sh redis:latest [--min-security=95]

OPTIONS:
    --debug                          Display the DEBUG logs
    --version                        Show the version
[..]

Meterian servers at https://acme.meterian.com/ are reachable from this system
Meterian servers are authorizing this client for account "QA Account"

```