Question: How to specify additionalProbingPaths for debugger

I am trying to debug in a docker container following the pattern described here: https://github.com/Microsoft/MIEngine/wiki/Offroad-Debugging-of-.NET-Core-on-Linux---OSX-from-Visual-Studio but using docker as the pipe program directly. This works as long as the code being debugged has been published.

However if I just map the build output into the container I get probing errors: e.g. An assembly specified in the application dependencies manifest (Demo.deps.json) was not found:

Adding --additionalProbingPath as a parameter in the "program" element doesn't work and I'm not able to find documentation on how to do it. Can you please advise?

In case it matters I'm using VisualStudio 15.5.6 and my launch.json is as follows
{ "version": "0.2.0", "adapter": "docker", "adapterArgs": "exec -i demo1 /vsdbg/vsdbg --interpreter=vscode", "languageMappings": { "C#": { "languageId": "3F5162F8-07C6-11D3-9053-00C04FA302A1", "extensions": [ "*" ] } }, "exceptionCategoryMappings": { "CLR": "449EC4CC-30D2-4032-9256-EE18EB41B62B", "MDA": "6ECE07A9-0EDE-45C4-8296-818D8FC401D4" }, "configurations": [ { "name": ".NET Core Launch", "type": "coreclr", "cwd": "/app", "program": "bin/Debug/netcoreapp2.0/Demo.dll", "request": "launch" } ] }

Start with the supplied launch.json, especially the coreclr configuration and docker adapter arguments, and review the linked Offroad Debugging wiki page. Determine where additionalProbingPath is supported for this launch configuration and document the correct setting or limitation for mapped build output. Done means the documented configuration addresses the probing error without requiring a published application.