I'm getting a Empty / bogus instruction is invalid

This is part of my dockerfile. This runs correctly in docker.

RUN apk update \
  # psycopg2 dependencies
  && apk add --virtual build-deps gcc python3-dev musl-dev \
  && apk add postgresql-dev \

I have multiple lines after this one that start with && and they do not have this error.

Can this be upgraded to the newer version of dockerlint?

Specifically because of a bug fixed:

RedCoolBeans/dockerlint#3

Every time I save a (valid) Dockerfile with this enabled, I get the following error message:

This is on macOS Sierra 10.12.1 in Atom 1.12.6 with dockerlint 0.2.0 installed globally via npm (the error happens both when I point linter-docker at this executable and when I leave it on the default). I have version 1.11.21 of the linter plugin installed.

Version 2.12.0 of eslint-plugin-import was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 0.3.5 of dockerlint was just published.

This version is covered by your current version range and after updating it in your project the build failed.

dockerlint is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid regExp for packageRules[0].packagePatterns: ^eslint``

This:

RUN apt-get install sudo

Throws unexpected warning:

sudo(8) usage found

Noticed via this Dockerfile

We need some form of CI added here to test that this is actually working.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update eslint packages (eslint-config-airbnb-base, eslint-plugin-import)
• chore(deps): update eslint packages (major) (eslint, eslint-config-airbnb-base)
• fix(deps): update dependency atom-package-deps to v8
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

The linter complains about WORKDIR calls that do not include absolute paths.

WORKDIR /
WORKDIR go

The linter complains about the second line above, however, the dockerfile reference documentation clearly states that WORKDIR calls with relative paths will result in the path relative to the previous WORKDIR calls.
https://docs.docker.com/engine/reference/builder/#workdir

In other words, this should be allowed. Why does the linter complain?

Please consider to add support for alternative docker linters, e.g. hadolint (http://hadolint.lukasmartinelli.ch/) which do much more checks than dockerlint.

Hello, I have noticed that dockerlint doesn't catch many issues in dockefile, such as the fact that base image name doesn't"t have a version or the maintainer is still used instead of using label etc... Is it possible to use lintter-docker with an alternative dockerfile linter npm package that I have used to great effects in my ci pipeline to better catch errors.

The current regex message parser does not include all kind of messages returned by dockerlint.

Empty file unparsed error: ERROR: /path/to/Dockerfile does not contain any instructions

Example 2:

RUN apt-get update

Unparsed error: ERROR: First instruction must be 'FROM', is: RUN

Example 3:

FROM someimage
CMD ["ls"]
CMD ["ls"]

Unparsed error: ERROR: Multiple CMD instructions found, only line 3 will take effect

Version 2.9.0 of eslint-plugin-import was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.18.0 of eslint was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This linter is awesome. It has an extensive static analytical abilities.

Would this linter be able to use that as its executable?

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 4.18.2 of eslint was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

As specified in Dockerfile reference:

# escape=\
# escape=`
The escape directive sets the character used to escape characters in a Dockerfile. If not specified, the default escape character is \.
The escape character is used both to escape characters in a line, and to escape a newline. This allows a Dockerfile instruction to span multiple lines. Note that regardless of whether the escape parser directive is included in a Dockerfile, escaping is not performed in a RUN command, except at the end of a line.
Setting the escape character to ` is especially useful on Windows, where \ is the directory path separator. ` is consistent with Windows PowerShell.

linter-docker does not currently check the escape directive and will report a line error if another character is used.

Hi there,
unfortunately I cannot get the plugin to work. Here's what I've done so far:

npm install -g dockerlint
npm install -g atom-linter
apm install linter-docker

I am still unsure about the following:

1. Which path do I have to enter for "Some executable path"?
2. How does my Dockerfile has to be named in order to be picked up by the linter? So does "Dockerfile" work for example?

Thanks a lot,
Sebastian

It looks like this linter does not currently have any specs written for it, adding it to the list being maintained here for tracking.

Specs do not need to be super detailed, as they should mainly test whether the package is properly running the linter plugin and parsing its messages. Leave testing of the linter functionality to the author of the linter.

If you need any help feel free to ask!

I'm not sure if anyone is still maintaining this plugin, but:
For linter-docker 0.1.4 with linter 1.11.21

I get the error Arguments to ENTRYPOINT in exec must not contain single quotes at line 2 col 1 for the following Dockerfile

FROM alpine:latest
ENTRYPOINT [ "/bin/bash" ]

This Dockerfile doesn't contain single quotes in it anywhere.