Jason Hall

@vdemeester Thanks for this explanation! Would it help if in this case the nop image had some basic command at `/bin/sh` that just exited regardless of args, the way the...

Oh my. This got complicated quickly! 😅 I'd be fine with providing common shebangs in the image. Sidecars that exit 1 upon teardown shouldn't fail the TaskRun anyway right? This...

I didn't think we were wrapping sidecar invocations in the entrypointer at all, but if we are (or if we decide to) then signaling via the downward API sounds simplest...

I don't think it should be possible to create a TaskRun with an invalid image name, since we parse and lookup the requested image in order to resolve the entrypoint....

That phrasing of the limit is surprising to me. The vanilla k8s [docs](https://kubernetes.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/#customizing-the-termination-message) say: > The termination message is intended to be brief final status, such as an assertion failure...

Oh I see, thanks for clarifying. In that case, it sounds like we should update the k8s docs so folks don't trip over this later. I'm sure I'll forget and...

I started https://github.com/knative/docs/pull/4524 trying to get the redirect set up for all repos automatically, and eventually pulled it back to just a couple repos based on review feedback. It should...

cc @jonjohnsonjr

v0.12 fixed a bug with KO_DOCKER_REPO=ko.local/foo which might be what you're describing. That should work and if not it's a bug we should fix

I've confirmed this behavior, and I believe it's a bug: ``` $ ko version 0.12.0 $ KO_DOCKER_REPO=ko.local/test ko build --bare ... ko.local:b892c8419de3e2b9729a50707a75ba8643fe56c704bfe5625dcc7c19f1741c5f ``` This should be `ko.local/test:b89...`