# verify-container

Validate container dependency inputs and optionally run docker build


## When to use it

Static verification is distinct from smoke=true, which invokes a Docker build. Inspect build context, dependency ownership, and deployment paths before enabling the smoke lane.

## Usage

Configure an Nx target on the owning project, then invoke it with `npm exec -- nx run <project>:<target>`. The executor identifier is not a standalone CLI command.

```json
{
  "targets": {
    "reviewed-action": {
      "executor": "@megamono/plugin:verify-container",
      "options": {}
    }
  }
}
```

This target is a configuration example. Supply required values and review side effects before invoking it.

## Options

Use these options with `@megamono/plugin:verify-container`. Nx uses the camelCase names shown here; the [CLI reference](/docs/cli) describes command-line aliases. Some options are required only for particular choices.

| Option | Required | Type | Default | Description |
| --- | --- | --- | --- | --- |
| `dockerfile` | No | string | "Dockerfile" | Workspace-relative Dockerfile path. |
| `context` | No | string | "." | Workspace-relative Docker build context. |
| `report` | No | string | — | Optional workspace-relative JSON report path. |
| `smoke` | No | boolean | false | Explicitly run docker build after static validation. |

## Next steps

Review changed files and run the affected project's checks. For options that accept structured values, run the generator's `--help` or consult the schema in the installed package.

- [All actions](/docs/actions)
- [CLI overview](/docs/cli)
- [Adopt an existing workspace](/docs/workflows/adoption)