How to Run and Debug Python Inside Docker Containers Using VSCode

[@Morten_Jaeger]

Note: The extension "Remote - Containers" is what nowadays is called "dev containers". They renamed it, that's all.

[@codevev]

Thanks for the update!

[@julianfernandez8117]

Thanks from Colombia!

[@codevev]

You're welcome! I play soccer with plenty of Colombians here in Vegas haha

[@mahmoudelzouka5689]

Thanks, Evgeny for the demo! this is what I was looking for.

[@codevev]

You're very welcome! Glad it helped!

[@bluesdog88]

Thanks for the run through, just what I was looking for!

[@codevev]

Glad I could help!

[@farmingbyfaith4210]

Awesome Video. Im busy with a project to use Python Data Science tools inside docker, but the tools then control metatrader inside wine. So I can have many algorithms running at once. I like the fact that I can debug line by line the Python code as it controls metatrader

[@codevev]

Sounds complicated :)

[@TechWazza]

Thanks for the this Evgeny...this was very simple, short and great help.

[@codevev]

You're welcome! Glad it helped!

[@JanM-u5r]

Mesjac stojal na meste poka nenašol eto video.
Spasibo.

[@irongranca]

Thanks from canary islands :)

[@codevev]

Awesome, you're welcome!

[@basicmachines]

Thanks. I couldn't find the 'Remote - Containers' extension in VS Code but I found something called 'Dev Containers' by Microsoft which sounds like the same thing. Has the name changed maybe?

[@codevev]

Just checked, Dev Containers from Microsoft extension does look correct!

[@codevev]

Correction. Dev Containers will probably work on its own but it's included in the Remote Development extension, which is a pack that not only lets you connect to Docker containers from VSCode but also ssh into other hosts

[@chennahoom]

Hey! Awesome video!
Just a quick question, when I reach the part after I click "Reopen in Container" ... I'm not getting the option to open "From Dockerfile" (7:22 in your video) , I get a list of configuration template. Do you know why maybe?

[@codevev]

Thanks! It looks like the option to open from dockerfile is only available when there's a Dockerfile that already exists in your workspace

[@jiangpengli86]

Thank you for this great tutorial.❤

[@codevev]

Glad it was helpful!

[@jarorkwong8042]

Thank you bro, nice and easy!

[@codevev]

Great! Glad it helped!

[@ahmedshawky9845]

Thanks mate, really appreciate it

[@codevev]

Anytime!

[@davidvc4560]

Thanks! Could you clarify if the VSCode actually created the container itself or connected to an existing container? @7:16. It looks like VSCode created a container to me, because it didn't ask for container name or id.

[@codevev]

It should have created a new container on its own

[@davidvc4560]

@@codevev thank you!

[@sg22r]

Pure GOLD!

[@codevev]

Thanks!

[@IFinging]

Fantastic video, Thank you

[@codevev]

Glad it helped!

[@alchemication]

This is nice, thank you, I just wonder if it could somehow work with K8s, so when your container dies, VS Code still works (as container would just simply restart) ... Also would be great to see version control integrated into this.

[@codevev]

Thanks! I haven't done much with K8s but let me know if you decide to try it out

[@emanueol]

uou manually installed python extension in the container, i wonder if its possible docker file to also do that ?

[@codevev]

Great question! You would do that in the devcontainer.json file rather than the Dockerfile

[@codevev]

Check this link out:
code.visualstudio.com/docs/devcontainers/containers#_adding-an-extension-to-devcontainerjson

[@emanueol]

@@codevev thanks 👍

[@devashishnigam5971]

How do we handle venv and requirements.txt. It would be great if you can cover that

[@codevev]

That's really the beauty of running Python inside the Docker container! You actually don't need venv because a container is an isolated environment. Hence, no special treatment of requirements.txt is needed but of course it depends on what exactly you're doing

[@ammadkhan4687]

Nice explanation. Thanks . Do you some some video to map network drive in docker container?

[@codevev]

Thanks! I don't have a video about mapping network drive to a container yet. I haven't used Docker much lately. Good luck!

[@danieltala9586]

Thanks! much better than debugpy :)

[@codevev]

I don't even know what debugpy is 😃

[@damircicic]

Hi when I click on the icon in the lower left corner and then click on any option in the list I get the message that current user does not have permission to run docker (I wanted to attach to the running container). Does anyone know how to solve this problem?

[@codevev]

Are you on windows? Try opening VSCode as administrator

[@damircicic]

@@codevev I am on Ubuntu. Sounds promising. Thanks! I'll give it a try.

[@codevev]

I see. Probably opening VSCode with 'sudo' could work. But maybe it's something else. I don't think I ever did it on Linux, just Windows or Mac

[@nedkapinill]

@@damircicic ​ I had same problem. I can open container with rootless in VS code. You can google "Run the Docker daemon as a non-root user (Rootless mode)" to fix permission problem.

[@3MandMatt]

would you add a video for docker compose?

[@codevev]

Anything in particular about it?

[@weishanlei8682]

There is no Remote-Containers extension. Please help!

[@codevev]

it should be Dev containers now I think

[@christiangunther650]

Hej Thx Evgeny! But could you explain the next steps on e.g. launch.json and how to configure properly? I have my problems there ... Cheers

[@codevev]

Christian, do you run into any specific problems? Mind sharing an error message or what is going on exactly?

[@pranitpawar2200]

after running build command getting below error:
failed to compute cache key: "/main.py" not found: not found

[@codevev]

You may have a typo in your Dockerfile. Sounds like it's not finding the path to the main.py file.

[@f0l1v31r4]

And does it work for framesworks like fastAPI, Flask and Django?

[@codevev]

Yes

[@sergeyasdf2677]

Hi there! How could I remote debugging on docker container?

[@codevev]

Did you watch the video?

[@UpToTheSkyAgain]

I appreciate your explanations. Very clear and the step by step procedure is very nice. However I don't manage to do the last part. I get and error reopening the project in the container :
[7105 ms] Start: Check Docker is running
[7105 ms] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[7177 ms] Server API version: 1.41
[7178 ms] Start: Run in Host: docker volume ls -q
[7225 ms] Host server: Error: spawn docker ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[7270 ms] Host server: (node:11049) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
(Use `node --trace-warnings ...` to show where the warning was created)
[7274 ms] Error: spawn docker ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
The only difference with you is that I did the first part already in a remote access, in SSH. However "reopen in container" is supposed to work. Any idea, welcome. :-)

[@codevev]

I think when you reopen in container, it just looks for Docker running on your local host. So if you hadn't installed it there, it can't find the running instance of Docker and is throwing an error. I'm actually not sure if what you're trying to do is supported, might be a good thing for me to try figuring out. But at my new job we aren't currently using docker containers and I do all of my development on an ec2 instance via remote ssh through VSCode😂

[@codevev]

If you want to learn how to connect from VSCode to a remote server via SSH, watch th-cam.com/video/titbwVSLCws/w-d-xo.html next

[@brunaguterres1817]

Unfortunatly there is no Remote - Containers extension on my VS code :(

[@codevev]

Bruna, you will need to install it first. You can follow this link: marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack

[@brunaguterres1817]

@@codevev Thank you so much. Nice tutorial. One of the most useful in TH-cam lately.

[@codevev]

Thanks for the kind words :)

[@mohasinsultan]

Thanks

[@bramjanssen8865]

This extension is now called: Dev Containers

[@codevev]

Thanks for the update!

[@codevev]

And to learn how to use VSCode on any other device, including your phone, watch th-cam.com/video/XcovoZWAdxE/w-d-xo.html

[@MentoriadeSoftware]

Hi codeEV,
Thanks for your video, I've done a test like you showed and everything works fine with the remote, but when I want to run my .py file I get an error:
Se produjo una excepción: ModuleNotFoundError
No module named 'matplotlib'
File "/workspaces/python/consulta.py", line 3, in
import matplotlib.pyplot as plt
This is my Dockerfile
FROM python:3.7.13
WORKDIR /home/tips/python
RUN pip install surprise
RUN pip install d2l==0.17.5
RUN pip install -U mxnet-cu101==1.9.1
RUN pip install seaborn
RUN pip install gluon
COPY . .
CMD [ "python", "./consulta.py" ]
This is the consulta.py file
import matplotlib.pyplot as plt #

[@codevev]

Hi! If I'm reading it correctly, the pip command to install matplotlib is missing from your dockerfile

[@julioalvia3619]

Thanks

[@codevev]

You're welcome!