Thanks so much for this video, I am new to using docker and I was very tired to have to delete and build the image manually every time I made a change into my code, now I have a better understanding of how docker works.
What if my docker-compose file creates 3 containers as such: 1- web app (Django) 2- db (Postgres) 3- nginx and i wanted to change some code in the Django files, without rebuilding everything and losing Postgres data?
I meaaaaaan, it's no different from compiling code. You can't run the old executable, or object files, and expect your new code changes to take affect. Is this really a difficult concept? Are compiled objects no longer taught in Comp. Sci or coding bootcamps? Anyway, I like the video it is a great explanation of an old concept.
I've been using docker for quite a bit time now, but it was only during watching this video I realised that the cookie cutter/template actually represents source code, and container is a compiled.exe that can be run... Then I read your comment :) Also I never heard such comparison before until today. Or even If I read one before, I didn't register it, because the idea wasn't communicated clear enough.
Thanks so much for this video, I am new to using docker and I was very tired to have to delete and build the image manually every time I made a change into my code, now I have a better understanding of how docker works.
Very Intuitive! Thank you
Perfect analogy
Thankyou so much for the an amazing explanation !!
Many thanks for this!
Bro, thank you very much, this is a really great vídeo and you have saved me!!!
Nice, thank you!
Das beste Video das ich zu dem Thema finden konnte und extrem gut erklärt
nice
Nice video I like those graphical explanations
What if my docker-compose file creates 3 containers as such:
1- web app (Django)
2- db (Postgres)
3- nginx
and i wanted to change some code in the Django files, without rebuilding everything and losing Postgres data?
need volume
@@AlexGower
I meaaaaaan, it's no different from compiling code. You can't run the old executable, or object files, and expect your new code changes to take affect. Is this really a difficult concept? Are compiled objects no longer taught in Comp. Sci or coding bootcamps? Anyway, I like the video it is a great explanation of an old concept.
I've been using docker for quite a bit time now, but it was only during watching this video I realised that the cookie cutter/template actually represents source code, and container is a compiled.exe that can be run... Then I read your comment :) Also I never heard such comparison before until today. Or even If I read one before, I didn't register it, because the idea wasn't communicated clear enough.