colin
colin copied to clipboard
user-cont
Tool to check generic rules/best-practices for containers/images/dockerfiles.
updates: - [github.com/asottile/pyupgrade: v2.37.3 → v3.2.2](https://github.com/asottile/pyupgrade/compare/v2.37.3...v3.2.2) - [github.com/psf/black: 22.6.0 → 22.10.0](https://github.com/psf/black/compare/22.6.0...22.10.0) - [github.com/pre-commit/mirrors-prettier: v2.7.1 → v3.0.0-alpha.4](https://github.com/pre-commit/mirrors-prettier/compare/v2.7.1...v3.0.0-alpha.4) - [github.com/pre-commit/mirrors-mypy: v0.971 → v0.991](https://github.com/pre-commit/mirrors-mypy/compare/v0.971...v0.991)
![pre-commit-ci[bot] avatar](https://avatars.githubusercontent.com/in/68672?v=4 "pre-commit-ci[bot] avatar"){kind=avatar}
based on https://github.com/user-cont/colin/pull/141 * replace rulest implementation by FMF references * allow to read colin command rulesets data via FMF * allow to do read dynamic checks, without fake classes
The Colin contributing guide states the following: ``` - Please make sure that your code complies with PEP8. - One line should not contain more than 100 characters. ``` This...
TODO: * [ ] As much checks as possible works with docker. Ideally utilize conu.
- [ ] `scratch` does not need a tag. - [ ] think about some exceptions for such Dockerfiles (or maybe also for base images).
Users do not need to have all requirements installed (e.g. you can use colin for Dockerfiles without installing podman). - [ ] It would be nice to have that approach...
# unittest dynamic class generator you can use this class file as dynamic generator for another scheduler like ``nosetest`` ``` $ TARGET=tests/data/Dockerfile nosetests unittest-run.py ... ---------------------------------------------------------------------- Ran 3 tests in...
Let's implement them using rootless containers which were recently merged into podman: https://github.com/projectatomic/libpod/pull/936 [podman-0.6.5+](https://github.com/projectatomic/libpod/pull/1029) This means that backend code for dynamic checks would utilize podman tool and the container would...
If there is a label defined in base image and the dockerfile does not overwrite it, the resulting image may contain incorrect metadata. This is a check only for dockerfiles....