News for hackers. Stuff that matters.
Re:Static Analysis for Dockerfiles by addcn on Thursday December 05, 2019 @06:16PM (#21717722)
Static analysis is great here — it’s definitely a constrained domain where it could shine w/o many of the issues that defined it a decade ago.

I bet you could take this a lot further by incorporating a runtime component as well. I mean it’s a container — it’s meant to be incrementally built up and destroyed.

By looking at the state of the container before and after a line you could do so much.

i.e. This innocent looking apt-get install has the side effect of making X directory writable.

Re:Static Analysis for Dockerfiles by simbakhadder on Thursday December 05, 2019 @04:36PM (#21716842)
This is smart, would love if it got smart enough to analyze .dockerignore files, and (if you're analyzing our code with the rest of your tool anyway) you could find large files/directories that we COPY/ADD and don't need
Re:Static Analysis for Dockerfiles by 1f60c on Thursday December 05, 2019 @07:38PM (#21718293)
What I do, is I start all my .dockerignores with "*" (i.e. ignore everything) and then selectively un-ignore the files and directories I need to copy.
Re:Static Analysis for Dockerfiles by dbaupp on Thursday December 05, 2019 @09:23PM (#21718751)
How does this differ to https://github.com/hadolint/hadolint ?