Hacker News Reader

Comment by akanet | Hacker News Reader

I once gave a lunch talk at Docker, inc, which included several slides of suggestions of features to add to Docker. Prominently featured was the request for a native command to clean old images. An engineer in attendance remarked incredulously that he could not believe that users would not know how to pipe docker ls into xargs docker rmi.

View on HN

I hate this mentality because.. what if there is no xargs? Don't just assume the standard scenario that everyone has this on their machine. Especially if your program is a statically linked "portable" go binary.

It's a sad, sad UNIX machine that doesn't even have xargs(1).

I dabble in embedded development, mainly as a hobby and I mainly deal with e-book reader devices.

Let me tell you this, if a device doesn't need a certain binary or tool, it ideally shouldn't be there. For security reasons etc. And with embedded devices with a specific purpose it's highly likely that there will be very little there.

But anyway, I was mainly saying that in principle this should be considered.

Guess he relented or isn't there anymore. docker images prune is really nice.

Hah, that's nothing. As far as I know, the command to update an existing configmap in Kubernetes looks like:

    kubectl create configmap foo --from-file foo.json -o yaml --dry-run | kubectl replace -f -

Talk about myopic.

Hence the need for either a) product managers or b) a no sociopath hiring policy.

Reply on news.ycombinator.com