Now that I have tested the code in one virtual environment, let me test it within another. NOTE: If pylint or your selected linter isn’t installed, it will prompt to be installed.Īs you can see, we can execute from the built-in terminal in VSCode and it is using my virtual environment. In this case, you’ll see the built-in Python’s that were found within PYTHONPATH and my virtual environments in /src/.venvs/ Now if I open a Python file, it will prompt me to select the Python interpeter I want to use.

Once it has been reloaded, you can open a directory. Click on the extensions icon and find Python.

Now that we’re attached to the container within VSCode, we’ll need to install and enable the Python extension within the container. Select the container you want to attach toĪ new window should have popped up and you should see that you’re attached to the container now.Select Remote-Containers: Attach to Running Container.Click on the >Now that is complete, you should be able to attach to a running container. Add the path in the container that your virtual environments are located in to the Python: Venv Path setting.Click File > Preferences > Settings within VSCode.

One of my use cases is that I have different Python Virtual Environments created in my docker image and I’d like to be able to use those to test code with different packages so i’ll show you how you can add custom paths for VSCode to search for virtual environments in. Search for Remote - Containers and click “Install”.Launch VSCode and click on the extensions icon.Let’s go ahead and get started on setting up VSCode with the Remote - Containers and Python extensions. I’ve been using using VSCode for development for a little while and was excited when Microsoft announced they were developing extensions to attach to running containers and allow you to still develop natively within Windows using VSCode.

Visual studio code virtualenv