There are several methods with how to instruct Dockle
to ignore specified checkpoints.
You can specify program parameters,
you can specify environment variables, and you can create a dockleignore file.
Because we're using Dockle in a continuous integration
environment, we're going to create a dockleignore file.
So let's head back to the console.
Let's create a file called dockleignore and only add the checkpoint that
was a false positive, and the full name was CIS‑DI‑0010.
So now, we created a dockleignore file.
In order to add the file to the repository, we need to specify
the parameter ‑‑force because all files starting with a dot are
specified in the gitignore file.
Now let's commit the file to the repository, again with a nice commit
message, and push the changes upstream to our GitLab server.
Let's switch to the web interface where GitLab picked up
the change and is running a new pipeline.
Let's click on the pipeline to see its details, and here you can see that
the lint stage now succeeded. As expected, it read our dockleignore file,
and the fatal message has now disappeared.
Mission succeeded.
We're now able to run Dockle in a continuous integration pipeline and
are able to configure it to weed out false positives.
What is up to you, of course, is go through each and any of the findings
and see whether they are actually applicable or not.
Let's summarize the use of Dockle in the next clip.