dockerfile_lint icon indicating copy to clipboard operation
dockerfile_lint copied to clipboard

Results 49 dockerfile_lint issues
Sort by recently updated
recently updated
newest added

# Feature request: In order to make the error more obvious, it would be nice to color them in red in the output. Like shellcheck does: ![image](https://user-images.githubusercontent.com/480586/44208550-f25e5180-a160-11e8-99f6-c10ab4364d96.png) Then as a...

fixing no_tag regex rule

If i don't have error then avoid any output, if i have errors then show their. I can do PR if your accept.

Currently in basic_rules_atomic.yaml, basic_rules.yaml, default_rules.yaml, openshift.yaml, osbs.yaml, the description for rule **no_tag** is _"lorem ipsum tar"_. It looks like a default description that was forgotten.

[https://github.com/projectatomic/dockerfile_lint/blob/a36b3008822a0b44303ddf1ad645e3327942450c/test/data/rules/basic.yaml#L7](url) The regex for the FROM rule causes false errors if the docker repo is on a non-standard port, for example: privaterepo.mine.com:1234/repo/name:tag This is a valid FROM parameter, but fails...

I tried to make the matching for "no_tag" more discrete and this appears to work, although no doubt a RegEx expert could improve it further. I discovered that using tags...

Replacing the default "lorem ipsum tar" with more explanatory text.

For [this Dockerfile](https://github.com/mohammedzee1000/postgres/blob/dockerfile.centos7-files/9.2/Dockerfile.centos7), one of the warning messages we get from linter is about lack of `yum clean all`. You can find complete logs [here](https://registry.centos.org/pipeline-logs/NmM3ZDg3YTE5Nj/linter_results.txt). But there's already a [`yum...

Many other dockerfile linters include a rule that the docker commands (FROM, RUN, etc) must be allcaps.

`CMD ['foo', '--bar']` will result in errors when running the docker image. it should be `CMD ['foo', '--bar']` . The rules should check this.