Used to parse Dockerfile build specs to infer their dependencies.
Config section: <span style="color: purple"><code>[dockerfile-parser]</code></span>
## Basic options
None
## Advanced options
<div style="color: purple"> <h3><code>version</code></h3> <code>--dockerfile-parser-version=<str></code><br> <code>PANTS_DOCKERFILE_PARSER_VERSION</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <code>dockerfile==3.2.0</code></span>
<br>
Requirement string for the tool.
</div> <br>
<div style="color: purple"> <h3><code>extra_requirements</code></h3> <code>--dockerfile-parser-extra-requirements="['<str>', '<str>', ...]"</code><br> <code>PANTS_DOCKERFILE_PARSER_EXTRA_REQUIREMENTS</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <code>[]</code></span>
<br>
Any additional requirement strings to use with the tool. This is useful if the tool allows you to install plugins or if you need to constrain a dependency to a certain version.
</div> <br>
<div style="color: purple"> <h3><code>interpreter_constraints</code></h3> <code>--dockerfile-parser-interpreter-constraints="['<str>', '<str>', ...]"</code><br> <code>PANTS_DOCKERFILE_PARSER_INTERPRETER_CONSTRAINTS</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <pre>[ "CPython>=3.7" ]</pre></span>
<br>
Python interpreter constraints for this tool.
</div> <br>
<div style="color: purple"> <h3><code>lockfile</code></h3> <code>--dockerfile-parser-lockfile=<str></code><br> <code>PANTS_DOCKERFILE_PARSER_LOCKFILE</code><br> </div> <div style="padding-left: 2em;"> <span style="color: green">default: <code><default></code></span>
<br>
Path to a lockfile used for installing the tool.
Set to the string `<default>
` to use a lockfile provided by Pants, so long as you have not changed the `--version
` and `--extra-requirements
` options, and the tool's interpreter constraints are compatible with the default. Pants will error or warn if the lockfile is not compatible (controlled by `[python].invalid_lockfile_behavior
`). See https://github.com/pantsbuild/pants/blob/release_2.8.1rc2/src/python/pants/backend/docker/subsystems/dockerfile_lockfile.txt for the default lockfile contents.
Set to the string `<none>
` to opt out of using a lockfile. We do not recommend this, though, as lockfiles are essential for reproducible builds.
To use a custom lockfile, set this option to a file path relative to the build root, then run `./pants generate-lockfiles --resolve=dockerfile-parser
`.
Lockfile generation currently does not wire up the `[python-repos]
` options. If lockfile generation fails, you can manually generate a lockfile, such as by using pip-compile or `pip freeze
`. Set this option to the path to your manually generated lockfile. When manually maintaining lockfiles, set `[python].invalid_lockfile_behavior = 'ignore'
`.
</div> <br>
## Deprecated options
None