Document how to debug applications about ko HOT 8 OPEN

The skaffold folks are doing some interesting work that we might be able to steal:

https://github.com/GoogleContainerTools/container-debug-support
GoogleContainerTools/skaffold#2306

from ko.

cc @Harwayne @ilackarms
xref: knative/eventing#1733

I think the short version is that you need a base image that contains ls and use the --disable-optimizations flag. We should definitely make this easier and document it, though.

from ko.

Can we enable remote debugging just packaging dlv and running the application with dlv? In a similar fashion to this: https://mikemadisonweb.github.io/2018/06/14/go-remote-debug/

from ko.

I think it's a good idea -- I prototyped something like this that would rewrite the base image and entrypoint to automagically drop you into a delve debugging session, but ultimately my lack of k8s/delve knowledge made me give up. It only worked ~30% of the time and leaked a bunch of connections/resources that were tough to clean up.

Getting the user experience correct here is tough, I think. We could make things incrementally better pretty easily, e.g. some way to just include delve in the produced binary is a good start.

from ko.

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

from ko.

/remove-lifecycle stale

from ko.

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

from ko.

/remove-lifecycle stale

from ko.