Docker Support or relative path option

[DellanX]

Is your feature request related to a problem? Please describe.
I'm running my client on Docker, and would like to be able to initiate my tests from vscode on my host machine.
I can almost do so, by changing the extension settings to call a different command; however, the filenames to test are incorrect for my docker machine.

Describe the solution you'd like
I think the easiest solution would be an options to setup a relative path mode.
Instead of passing the file "/home//repos//tests/a.test.ts", passing "tests/a.test.ts"
Or a way for me to remap "/home//repos//" to whatever file structure the docker image is using (less preferred)

Describe alternatives you've considered
I am going to see if I can get my other extensions to work on the docker container, then I could just run this extension directly on the image.

Additional context
I'm developing using Laravel Sail, so all I needed to do was change the command option to "sail npm run test" to get the extension to call into my docker container. That being said, the paths are still incorrect.

[scurry222]

My exact question, thanks for bringing this up.

What extension setting did you use to stay within your container?

[DellanX]

Right now I am using ms-vscode-remote.remote-containers to remote into my dev container.

While it does work, I have a few tools that need to be ran from outside the container. There are also some extensions that used to not run correctly on the container; however, are working fine now.

[sheremet-va]

If you can provide a step-by-step guide on how to setup such environment, I can take a look if it's possible to implement it with our new architecture.