Implement a linter for the rules

[nuest]

• check out existing Dockerfile linters - do they solve (part of) the challenges?
• can they be extended to give warnings for specific behaviour?
• can they be configured so that rules unfavourable for reproducibility are not used?
• what kind of tests do they do?
• what are common rules?

---

• https://www.fromlatest.io/#/ | https://github.com/replicatedhq/dockerfilelint
• https://www.dockerfilelint.com/#/ | https://github.com/TheYorkshireDev/dockerfilelint.com (fork of the previous one)
• https://hadolint.github.io/hadolint/ | https://github.com/hadolint/hadolint
• https://github.com/projectatomic/dockerfile_lint
  • custom rules files
• https://github.com/redcoolbeans/dockerlint
• https://github.com/jeromepin/whale-linter
• https://github.com/zabio3/godolint
• https://github.com/microsoft/vscode-docker

https://github.com/search?q=dockerfile+linter

[nuest]

@psychemedia has some comments in #33. My reply:

I think using any linter for readability and to avoid stupid mistakes is something we can recommend. A linter will also help with formatting consistency, so that a Dockerfile under version control will be tracked more effectively, i.e., in a more readable way.

Building upon that, we could provide a linter with special rules concerning reproducibility in a scientific context. IMO the policing is thinking too far ahead right now.

[vsoch]

I've never used a linter, but I'm definitely interested to follow along here!

[nuest]

Looking at the list of linters again, the custom rules of https://github.com/projectatomic/dockerfile_lint could be a starting point for our own linter.