Validate your Python code.
In order to use this container as a part of my CI/CD pipeline for Python
projects, I needed to have proper exit code - 0 - if there are no errors.
That is why I used pylint-exit as an addition to pylint, to capture
exit status of pylint, and handle it before 'real' exit.
This container allows to pass custom requirements.txt file.
By default, config directory is mount in container and
requirements-default.txt is installed.
You can add another file to the config directory, and execute it during
running image. Example below.
In order to have proper environment for check, you can build this container
by yourself, adding needed packages to the requirements.txt file before
build.
pylint and pylint-exit must stay there.
Or use the custom-config ability, described below.
In order to pull the image, run:
docker pull almerhor/pylint
In order to build the image by your own, run:
docker build -t pylint .
In order to run the container and check the code, execute:
docker run --rm -v $(pwd)/directory:/pylint pylint \
path_to_the_file_or_module
Where $(pwd)/directory is a place with Python files to lint.
If additional requirements file need to be passed, run:
docker run --rm -v $(pwd):/pylint \
-v $(pwd)/custom-config:/tmp/custom-config \
pylint \
path_to_the_file_or_module requirements-custom.txt
Must have:
- directory
custom-configwith your custom requirements file - mount this directory under
/tmp/custom-configinside container.