Тёмный

How to Run and Debug Python Inside Docker Containers Using VSCode 

codevev
Подписаться 1,5 тыс.
Просмотров 55 тыс.
50% 1

You don't need to have Python installed on your system in order to run it. Replace Python with almost any other language and keep your computer free from all the things you need to have installed in order to start developing software!
Version collisions are in the past. Create a docker image for each of your projects that you're working on and you will not have to spend hours or days fixing a local environment because you upgraded a package that broke everything.
In this video, I will show you a couple of ways to run Python in a Docker container, and in the end, we will set up VSCode (Visual Studio Code), so you could run and debug your code inside a container without leaving VSCode!
Timeline:
0:00 Why do you want to run code inside a container
0:45 How to run Python in Docker using an interactive terminal
3:00 Create a Docker file to create an image and run your Python code using docker commands
6:10 How to connect Visual Studio Code to a Docker container to run Python code
#SoftwareEngineering #Python #Docker
-------------------------------------------------------------------------------------
📰 Sign up for my newsletter
Become a better dev in just 5 minutes (or so) a week: codevev.com
🖥️ Free Courses to Learn Programming
Harvard CS 50: pll.harvard.edu/course/cs50-i...
FreeCodeCamp: www.freecodecamp.org
Udacity: www.udacity.com
🛒 Products I recommend
codevev.com/#products
Connect with me
Website: codevev.com
RU-vid: / @codevev
#codevev
Connect with me
Website: evgenyurubkov.com
RU-vid: / @codevev
#codevev

Опубликовано:

 

6 май 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 66   
@codevev
@codevev 3 месяца назад
If you want to learn how to connect from VSCode to a remote server via SSH, watch ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-titbwVSLCws.html next
@mahmoudelzouka5689
@mahmoudelzouka5689 3 года назад
Thanks, Evgeny for the demo! this is what I was looking for.
@codevev
@codevev 3 года назад
You're very welcome! Glad it helped!
@TechWazza
@TechWazza 2 года назад
Thanks for the this Evgeny...this was very simple, short and great help.
@codevev
@codevev 2 года назад
You're welcome! Glad it helped!
@farmingbyfaith4210
@farmingbyfaith4210 2 года назад
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
@codevev 2 года назад
Sounds complicated :)
@bluesdog88
@bluesdog88 3 месяца назад
Thanks for the run through, just what I was looking for!
@codevev
@codevev 3 месяца назад
Glad I could help!
@jarorkwong8042
@jarorkwong8042 2 года назад
Thank you bro, nice and easy!
@codevev
@codevev 2 года назад
Great! Glad it helped!
@ahmedshawky9845
@ahmedshawky9845 Год назад
Thanks mate, really appreciate it
@codevev
@codevev Год назад
Anytime!
@irongranca
@irongranca 2 года назад
Thanks from canary islands :)
@codevev
@codevev 2 года назад
Awesome, you're welcome!
@IFinging
@IFinging 2 года назад
Fantastic video, Thank you
@codevev
@codevev 2 года назад
Glad it helped!
@sg22r
@sg22r 9 месяцев назад
Pure GOLD!
@codevev
@codevev 9 месяцев назад
Thanks!
@alchemication
@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
@codevev Год назад
Thanks! I haven't done much with K8s but let me know if you decide to try it out
@chennahoom
@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
@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
@ammadkhan4687
@ammadkhan4687 Месяц назад
Nice explanation. Thanks . Do you some some video to map network drive in docker container?
@codevev
@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!
@basicmachines
@basicmachines 4 месяца назад
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
@codevev 4 месяца назад
Just checked, Dev Containers from Microsoft extension does look correct!
@codevev
@codevev 4 месяца назад
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
@christiangunther650
@christiangunther650 2 года назад
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
@codevev 2 года назад
Christian, do you run into any specific problems? Mind sharing an error message or what is going on exactly?
@mohasinsultan
@mohasinsultan 2 года назад
Thanks
@devashishnigam5971
@devashishnigam5971 2 года назад
How do we handle venv and requirements.txt. It would be great if you can cover that
@codevev
@codevev 2 года назад
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
@danieltala9586
@danieltala9586 2 года назад
Thanks! much better than debugpy :)
@codevev
@codevev 2 года назад
I don't even know what debugpy is 😃
@davidvc4560
@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
@codevev Год назад
It should have created a new container on its own
@davidvc4560
@davidvc4560 Год назад
@@codevev thank you!
@3MandMatt
@3MandMatt Месяц назад
would you add a video for docker compose?
@codevev
@codevev Месяц назад
Anything in particular about it?
@f0l1v31r4
@f0l1v31r4 10 месяцев назад
And does it work for framesworks like fastAPI, Flask and Django?
@codevev
@codevev 10 месяцев назад
Yes
@emanueol
@emanueol Год назад
uou manually installed python extension in the container, i wonder if its possible docker file to also do that ?
@codevev
@codevev Год назад
Great question! You would do that in the devcontainer.json file rather than the Dockerfile
@codevev
@codevev Год назад
Check this link out: code.visualstudio.com/docs/devcontainers/containers#_adding-an-extension-to-devcontainerjson
@emanueol
@emanueol Год назад
@@codevev thanks 👍
@sergeyasdf2677
@sergeyasdf2677 Год назад
Hi there! How could I remote debugging on docker container?
@codevev
@codevev Год назад
Did you watch the video?
@UpToTheSkyAgain
@UpToTheSkyAgain 6 месяцев назад
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
@codevev 6 месяцев назад
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😂
@pranitpawar2200
@pranitpawar2200 Год назад
after running build command getting below error: failed to compute cache key: "/main.py" not found: not found
@codevev
@codevev Год назад
You may have a typo in your Dockerfile. Sounds like it's not finding the path to the main.py file.
@damircicic
@damircicic 2 месяца назад
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
@codevev 2 месяца назад
Are you on windows? Try opening VSCode as administrator
@damircicic
@damircicic 2 месяца назад
@@codevev I am on Ubuntu. Sounds promising. Thanks! I'll give it a try.
@codevev
@codevev 2 месяца назад
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
@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.
@brunaguterres1817
@brunaguterres1817 Год назад
Unfortunatly there is no Remote - Containers extension on my VS code :(
@codevev
@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
@brunaguterres1817 Год назад
@@codevev Thank you so much. Nice tutorial. One of the most useful in RU-vid lately.
@codevev
@codevev Год назад
Thanks for the kind words :)
@MentoriadeSoftware
@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
@codevev Год назад
Hi! If I'm reading it correctly, the pip command to install matplotlib is missing from your dockerfile
@julioalvia3619
@julioalvia3619 Год назад
Thanks
@codevev
@codevev Год назад
You're welcome!
Далее
Debugging a Dockerized Django app with VSCode
23:22
Просмотров 34 тыс.
How to debug Docker containers! (Python + VSCode)
9:24
25 nooby Python habits you need to ditch
9:12
Просмотров 1,7 млн