Repository navigation
Include build context structure when debugging with DAP #3368
Description
Activity
This should work for a file system or when building with a tarball as a context. I know other types of build contexts are supported as well but not sure which other ones make sense.
I think this currently works but I just tested it on the change included in #3450 and it definitely works there. If you're on a
COPYinstruction and check the file explorer, you'll see two digests which correspond to the place you're copying from and the place you're copying to. You have to look inside right now to figure out which is which, but it is possible.I'm thinking to add a bit of a user-facing change that makes the most common situation a bit easier which is identifying sources.
Description
When using DAP, I can navigate the file system through the variables view of my DAP client. It would be nice if we could add a node to show the "build context". Lots of Dockerfiles use a simple
COPY . .but people may not realize what's actually in the build context because of the.dockerignorefile. Showing the build context when debugging could help demystify this.