I've even tried doing that with all the devtools we have. Like normally a developer here has to install gcloud, terraform, kubectl, apt-get lots of stuff, and then 3-4 internal tools. Then configure all of it, and of course some stuff will just not work on someone's computer. But creating a docker image including all that means that I can grab a new computer and be up and running in minutes.
I did some googling, but I’m unfortunately not experienced enough to be able to describe the problem succinctly to google.
Using pylance, btw.
TIA!
This works in VSCode over SSH perfectly fine - the locally running VSCode is able to detect and select Python environments in the remote server.
Although, now you’ve got me thinking what would happen if I mounted the interpreter inside the container to something local that I can point to? Might try this later, thanks for the help!
"Setting up a Python environment" takes about 10 minutes and it's dead nuts reliable.
It is a very effective package manager.
Conversely, the experience of using Ruby within Docker for development is often clunky and awkward by comparison.