dockerfile-parser
Used to parse Dockerfile build specs to infer their dependencies.
Backend: pants.backend.docker
Config section: [dockerfile-parser]
Basic options
None
Advanced options
dockerfile==3.2.0
Requirement string for the tool.
extra_requirements
extra_requirements
--dockerfile-parser-extra-requirements="['<str>', '<str>', ...]"
PANTS_DOCKERFILE_PARSER_EXTRA_REQUIREMENTS
[]
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.
interpreter_constraints
interpreter_constraints
--dockerfile-parser-interpreter-constraints="['<str>', '<str>', ...]"
PANTS_DOCKERFILE_PARSER_INTERPRETER_CONSTRAINTS
[ "CPython>=3.7,<4" ]
Python interpreter constraints for this tool.
<default>
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.12.1/src/python/pants/backend/docker/subsystems/dockerfile.lock 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
.
As explained at Third-party dependencies, lockfile generation via generate-lockfiles
does not always work and you may want to manually generate the lockfile. You will want to set [python].invalid_lockfile_behavior = 'ignore'
so that Pants does not complain about missing lockfile headers.
Deprecated options
None
Updated over 1 year ago