Replies: 1 comment
-
I did a bunch of research and I figured out how to do it, but it seems a little kludgey...
"remoteEnv": {
"hostWorkspaceFolder":"${localWorkspaceFolder}"
}, Now I can refer to the workspace folder on the host as |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have to call out to a program that resides outside my container. It wants to work on a source file I'm updating in my dev container, but I don't know how to describe the host file path to the external program from inside my container without hardcoding the file path.
I noticed in the container launch logs, you are actually keeping inventory of the folder that maps to
workspaces/<folder>
asdevcontainer.local_folder
.-l devcontainer.local_folder=/home/zak/Development/GitHub/blues/note-zephyr
Is there a way I can read that metadata from inside the container (specifically from
tasks.json
) today? If not, I would like to request this as a feature.Beta Was this translation helpful? Give feedback.
All reactions