GoLand and Docker: which debug workflow should target the image you ship?
The goal is to standardize one debugging workflow for a Go service whose production artifact is a container image, using GoLand's bundled Docker integration: a daemon connection over a Unix socket, Windows named pipe, or TLS-secured TCP, plus the Services tool window and Docker Compose support. Assuming a recent GoLand release (2024.x or newer); behavior var