You may want to use https://github.com/orijtech/httperroryzer for your CI.

I invite you to read https://unix.stackexchange.com/q/169716/38906

Why official docker client don't have list image tags feature?

It's great! Using:

    </dev/urandom hexdump -v -e '/1 "%u\n"' | ...

save you from spawning one process.

Great work!

PS: You need gawk to run this.

And you need non-standard feature `-print0` and `xargs -0` there. Better way should be `find ... -exec cmd {} +`.

Is there a place you can use `-exec cmd {} +` but not `print0`? My experience has been I can use both or I can use none (Solaris 10 boxes).

Systems with a non-GNU find, including the default one in Solaris 10 (I've just double-checked). Perhaps you were using the GNU find in Solaris?

By the way, there are systems where 'print0' is a recognized parameter for the default find, but not '+'. RHEL 4.x comes to mind.

Sorry I think we're saying same thing. On systems with non-GNU find do either `-exec cmd {} +` or `print0` work? My exp was both did NOT work. So either both work or both don't.

But if I understand you correctly on RHEL 4.X `print0` works but `-exec cmd {} +` doesn't.

Which is to say I disagree with op that it's better to rely on `exec cmd {} +` when it seems you're more likely to have `print0 and xargs -0` then that.

And you also want to prevent `while` loop in shell script. See http://unix.stackexchange.com/q/169716/38906 for more details.

It's said that all the example was missing quoting variables. It made all others defensive things useless.