News for hackers. Stuff that matters.
Re:The sad state of sysadmin in the age of containers (2015) by GordonS on Monday December 09, 2019 @08:42AM (#21742510)
> A lot of them involve messy build steps, including downloading binaries or source tarballs without verification

Do they though?

Whenever I write Dockerfiles that depend on external downloads, I always check the hash matches one baked into the Dockerfile itself, and I've always seen others doing the same.

Re:The sad state of sysadmin in the age of containers (2015) by takeda on Monday December 09, 2019 @10:55AM (#21743655)
I have seen this many times, generally the high profile containers do that, and these issues are more common among my peers. This requires self discipline and containers were pushed as a panacea for environments where the discipline is lacking.
Re:The sad state of sysadmin in the age of containers (2015) by gmueckl on Monday December 09, 2019 @12:34PM (#21744517)
What is the point of storing the hash of an external file instead of checking the file into local version control? You're making it a part of your sources either way.
Re:The sad state of sysadmin in the age of containers (2015) by takeda on Tuesday December 10, 2019 @11:55PM (#21759701)
People who want to run docker don't want to run artifactory.

I'm not saying it's a good thing, but that's what I observed.

Re:The sad state of sysadmin in the age of containers (2015) by GordonS on Monday December 09, 2019 @03:10PM (#21745973)
Do you have any examples of high-profile images that do this?

I really just haven't seen this with the ones I use.

Re:The sad state of sysadmin in the age of containers (2015) by takeda on Tuesday December 10, 2019 @11:45PM (#21759664)
Sorry, I see that my response looks ambiguous.

I meant the opposite. The high profile containers generally do the right thing, but containers created by peers rarely do it.

There's no mechanism to make things reproducible you need to implement it yourself, and from my experience most people (not the ones that release something publicly, but ones that work for a companies that use it) don't do it.