News for hackers. Stuff that matters.
Re:Ask HN: Who operates at scale without containers? by treis on Tuesday March 22, 2022 @05:23PM (#30771756)
>Getting repeatable docker images

But there's no real need for repeatable build docker images. You copy the image and run it where ever you need to. The entire point of Docker is to not have to repeat the build.

Re:Ask HN: Who operates at scale without containers? by hinkley on Tuesday March 22, 2022 @06:11PM (#30772242)
If you could explain that to the Docker team you would be performing a great humanitarian service.

They for many years close issues and reject PRs based on the assertion that Dockerfile output needs to be repeatable (specifically, that the requested feature or PR makes it not repeatable). It’s not, it can’t be without a time machine, and if it was I believe you’d find that ace icing traction would have been more difficult, even impossible.

Re:Ask HN: Who operates at scale without containers? by treis on Tuesday March 22, 2022 @07:21PM (#30772895)
Do you have an example?
Re:Ask HN: Who operates at scale without containers? by spion on Tuesday March 22, 2022 @09:08PM (#30773677)
Until there is a critical vulnerability in one of the components present on that image (system packages or application packages).
Re:Ask HN: Who operates at scale without containers? by kronin on Wednesday March 23, 2022 @12:17AM (#30774885)
This is why I haven't adopted the practice of "Build your artifact along with the docker image that packages it".

Instead, build your artifact and publish it to an artifact repository, just like we used to.

_then_ wrap that artifact in a Docker image.

Vulnerability found in the docker image? No problem. Build a new image with the same artifact.

Re:Ask HN: Who operates at scale without containers? by barbazoo on Thursday March 24, 2022 @01:49PM (#30793206)
I'm curious why you're being downvoted for this. Whoever disagrees, please share some context.

What you said about "wrapping" I interpret as: based on an image for instance with OS level dependencies you create another image with application level artifacts, e.g. a python application. When your app changes, you don't build the base image again, you only build the app image. This makes sense to me.

Re:Ask HN: Who operates at scale without containers? by treis on Wednesday March 23, 2022 @10:45AM (#30778969)
At that point you're not repeating a build. You're building a new image.
Re:Ask HN: Who operates at scale without containers? by spion on Wednesday March 23, 2022 @11:42AM (#30779642)
From that point on, the build may become "fully unrepeatable" because previous steps may have reused cached stuff that can no longer be reproduced.

You could break the build simply by cleaning some things from the cache, without changing the Dockerfile, even thought that Dockerfile "succeeded to build"

Re:Ask HN: Who operates at scale without containers? by convolvatron on Wednesday March 23, 2022 @01:38PM (#30781107)
what happens when you need to create a new one with a small incremental change?