Docker: Using Docker as a Remote Interpreter
This feature is only supported in the Professional edition.
The following is only valid when Docker integration and Python Docker plugins are installed and enabled!
PyCharm integration with Docker allows you to run your applications in the variously configured development environments deployed in Docker containers.
Make sure that the following prerequisites are met:
- Docker is installed, as described on the page Docker Docs. You can install Docker on the various platforms, but here we'll use the Windows installation.
Before you start working with Docker, make sure that the Docker Integration and Python Docker plugins are enabled. The plugins are bundled with PyCharm and activated by default. If the plugins are not activated, enable them on the Plugins settings page of the Settings / Preferences Dialog as described in Enabling and Disabling Plugins.
- Also, for Windows, right-click the Docker whale icon, choose Settings on the context menu, and in the General page select the Expose daemon... checkbox:
Preparing an example
Create a Python project
QuadraticEquation, add the
quadratic_equation.py file and enter the following code:
import math class Solver: def demo(self, a, b, c): d = b ** 2 - 4 * a * c if d > 0: disc = math.sqrt(d) root1 = (-b + disc) / (2 * a) root2 = (-b - disc) / (2 * a) return root1, root2 elif d == 0: return -b / (2 * a) else: return "This equation has no roots" if __name__ == '__main__': solver = Solver() while True: a = int(input("a: ")) b = int(input("b: ")) c = int(input("c: ")) result = solver.demo(a, b, c) print(result)
Configuring Docker as a remote interpreter
Now that we've prepared our example, let's define a Docker-based remote interpreter.
To do it, open the Settings dialog (press Ctrl+Alt+S or click on the main toolbar).
Next, click the Project Interpreter page, on this page click next to the Project Interpreter field, and choose Add Remote from the drop-down list:
In the dialog box that opens, select the Docker option, from the drop-down lists select the Docker server (if the server is missing, click New...) and image name.
Python interpreter path should have the default value:
As a result, in the Settings dialog, you should see something like this:
Apply changes and close the dialog.
Running your application in a Docker container
In the left gutter, next to the
main clause, click the button, and choose Run 'quadratic_equation.py' command. You see that your script runs in the Docker container:
As you can see, the prefix in the Run tool window shows the container ID.
Debugging your application in a Docker container
Next, let's debug our application. For that, let's put a breakpointon the line that calculates
d, then click and choose .
As you see in the Console tab of the Debug tool window, the debugger runs also in the Docker container:
But now this container has a different id, and hence - different name. You can see it in the Terminal: type the
docker ps command and see the container id and name:
Docker tool window
But is it possible to see all the containers without the Terminal? PyCharm says - yes. You can use the Docker Tool Window as the UI for the Docker command-line client.
If you have configured Docker as a remote interpreter, you will see the Docker tool window button at the bottom side of the main PyCharm window:
Click this button and see that the Docker tool window opens:
Let's look at this tool window more attentively. What do we see here?
- First, we are connected to a Docker daemon:
- Second, if we open the Run tool window, we'll see that the Docker prefix corresponds to the container ID in the Properties tab of the Docker tool window:
- Third, if we open the Debug tool window, we'll see that the Docker prefix (another one!) corresponds to the another container ID in the Properties tab of the Docker tool window:
- And finally, we see the strange names of the containers - they are human-readable and generated by Docker itself.
Let's summarize what has been done with the help of PyCharm:
- We created a project and added a Python script.
- We configured the remote interpreter.
- We ran and debugged our script in the Docker containers.
- Finally, we launched the Docker tool window and saw all the details visible in the Terminal.