Skip to content

Conversation

@jsternberg
Copy link
Collaborator

The debug adapter will now look at the error and collect the input
mounts from the exec operation and translate them to a gateway reference
to be able to access the filesystem in the file explorer.

When we are attempting to find the real operation that failed and
succeed, we now re-solve the dependencies (which should already have
been solved correctly to begin with) so that we can have the proper
reference and can access the filesystem contents.

Fixes #3403.

@crazy-max crazy-max added this to the v0.29.0 milestone Sep 8, 2025
…on an error

The debug adapter will now look at the error and collect the input
mounts from the exec operation and translate them to a gateway reference
to be able to access the filesystem in the file explorer.

When we are attempting to find the real operation that failed and
succeed, we now re-solve the dependencies (which should already have
been solved correctly to begin with) so that we can have the proper
reference and can access the filesystem contents.

Signed-off-by: Jonathan A. Sternberg <[email protected]>
@jsternberg jsternberg force-pushed the dap-file-explorer-on-error branch from eb47477 to 17c2e1d Compare September 17, 2025 20:58
@tonistiigi tonistiigi merged commit 77315f9 into docker:master Sep 17, 2025
138 checks passed
@jsternberg jsternberg deleted the dap-file-explorer-on-error branch September 18, 2025 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DAP: Filesystem explorer should work when an error is encountered

3 participants