0:09 - what is a container technically? 1:16 - demo This is a full kubernetes tutorial including docker basics - check out the full playlist ua-cam.com/play/PLy7NrYWoggjwPggqtFsI_zMAwvG0SqYCb.html and subscribe to get notified about new videos
amazing content. docker is new territory and I am definitely learning a lot from these series. i will definitely subscribe to this channel, just pure content
Hi Nana, thank you for these very informative video series. I really appreciate your way of teaching. It's not too basic and not too complex. Just the way it should be for me :)
the shared layers save space too, anything that is read-only can be shared. this makes the technology more attractive that something like virtual machines that don't share and are heavy.
Is it accurate to say that a docker image is just a template of the environment you want (with the OS/App/App dependencies etc) and a container is a running instance of this IMAGE?
Very nice tutorial, thank you! I'm just thinking what would happen if service would call postgres at 5432 port (becase 2 containers work in same port here). Nevertheless - nice explained, diving into next tutorial episodes
Thanks a lot. Appreciate the feedback! good observation with ports. However it can't happen. Because with THIS setup, none of the containers are actually accessible by any service. So if you do "lsof -i :5432" nothing will be listening on that port. The reason: even though both containers are running on 5432, they aren't bound to the ports on your laptop/PC. But I explain exactly that in this video (min 10:00): ua-cam.com/video/xGn7cFR3ARU/v-deo.html So if you are watching the whole series you'll get there :)
@@TechWorldwithNana Now I get it. I came back to this comment to update it that it is well explained in tutorial 4 what you just mentioned. Thanks for the explanation here - might be usefull for other people who are before tutorial 4. Cheers
I am quite late to learn this but This is very good. i have a question , for suppose we have 2 images of same software eg postgress, So how the port of operation is decided. Like default port of both will be changed right? Then how i can check that and work accordingly. I hope i make sense?
Both postgres 9.6 and 10.10 are running on the ports 5432. Are these ports on the host machine or are they on the two individual containers. This is a common question asked and it will be nioce if you could please clarify. Otherwise it is a great lecture series. I have subscribed and liked!! :)
Hi ,Thank you for posting the tutorial, it helping me a lot and learning new concepts. thank you so much again. i have query on docker image i.e. In tutorial,at one point explained Docker Image package the all the dependencies. what is mean to it dependencies of what kind could you please elaborate bit more clear. Thank you
This is the message I get when I try to docker run postgre: Error: Database is uninitialized and superuser password is not specified. You must specify POSTGRES_PASSWORD for the superuser. Use "-e POSTGRES_PASSWORD=password" to set it in "docker run". You may also use POSTGRES_HOST_AUTH_METHOD=trust to allow all connections without a password. This is *not* recommended. See PostgreSQL documentation about "trust": www.postgresql.org/docs/current/auth-trust.html I realize this is by design (according to the postgre image developers). I've tried setting the -e parameters on the docker run line but the message still persists and I'm not able to start the container. Anyone else figured out a workaround?
I tried this with maven latest image. It pulled everything but the image is not running and I am not able to locate docker/library/maven section on my ubuntu linux machine
How is it possible to run 2 containers from different image versions on same port, I agree internally they can use same port but how it is exposed to hostmachines? @Nana
you should learn the internals of this. these layers are actually the layers of unionfs file system. each line in a dockerfile creates a new layer. an image is a set of read only unionfs layers, compressed. when a container is created, a new writable unionfs layer is added on top of read only layers that come from image. container process isolation is done by linux cgroups and namespaces etc.
0:09 - what is a container technically?
1:16 - demo
This is a full kubernetes tutorial including docker basics - check out the full playlist ua-cam.com/play/PLy7NrYWoggjwPggqtFsI_zMAwvG0SqYCb.html and subscribe to get notified about new videos
This is the best Docker tutorial series I have ever watched. Well explained at a great pace! Thank you, Nana!
Thank you. I'm so glad I ran across your video series. I love your attention to detail.
Thanks Ken! :)
Whenever I need any information on containers and DevOps, this is my go to channel. Thank you so much for creating such an amazing training channel
amazing content. docker is new territory and I am definitely learning a lot from these series. i will definitely subscribe to this channel, just pure content
Hi Nana, thank you for these very informative video series. I really appreciate your way of teaching. It's not too basic and not too complex. Just the way it should be for me :)
Glad that the series have helped you Umit. 🙂
the shared layers save space too, anything that is read-only can be shared. this makes the technology more attractive that something like virtual machines that don't share and are heavy.
Thanks a lot Nana !!
Love your short and detailed tutorials..!!
thank you! I love that its concise and to the point.
Appreciate the compliment! 😇
Thank you for the efforts you put up to train developer community. This helped me.
You're welcome, glad I can help! if you want to support me, please share and spread the word :)
THANKYOU SO MUCH !Your videos helped me a lot!
Only created an account to leave a like and subscribe and comment, you do a great job !
This is so sweet. Thank you! 🙂
Thanks a lot for those great tutorials !
Thank you 🙏 so much Nana for these!!
Great Explanation! Thanks for the video Nana
Just great, thanks a million! Keep up the good work Nana!
Thanks for explaining the diff between container and image 👍
Informative. Thank you.
Big Thank for the clear explanation👍👍
Thank you for this very good explanation
Is it accurate to say that a docker image is just a template of the environment you want (with the OS/App/App dependencies etc)
and a container is a running instance of this IMAGE?
Yes, that's an absolutely correct comparison I would say!
wonderful explanation. really good video.
thankyou very much it really helps me
Hi Louis, I'm glad this has helped you. Best of luck in your career. 🙂
Very nice tutorial, thank you! I'm just thinking what would happen if service would call postgres at 5432 port (becase 2 containers work in same port here). Nevertheless - nice explained, diving into next tutorial episodes
Thanks a lot. Appreciate the feedback! good observation with ports. However it can't happen. Because with THIS setup, none of the containers are actually accessible by any service. So if you do "lsof -i :5432" nothing will be listening on that port. The reason: even though both containers are running on 5432, they aren't bound to the ports on your laptop/PC. But I explain exactly that in this video (min 10:00): ua-cam.com/video/xGn7cFR3ARU/v-deo.html
So if you are watching the whole series you'll get there :)
@@TechWorldwithNana Now I get it. I came back to this comment to update it that it is well explained in tutorial 4 what you just mentioned. Thanks for the explanation here - might be usefull for other people who are before tutorial 4. Cheers
@@krzysiek5806 Thanks for updating your comment! :)
Awesome tutorial
Nana, Good job
Thank you !! I like it is a lot.
Thanks again Mat! :)
I am quite late to learn this but This is very good. i have a question , for suppose we have 2 images of same software eg postgress, So how the port of operation is decided. Like default port of both will be changed right? Then how i can check that and work accordingly. I hope i make sense?
I'm new to docker. You can run the same application with different versions without any conflict but is there a use case for that?
Thank you nana well explained
Totally Loved it thank u sm for uploading 😍
Nice video
Fantastic!
Both postgres 9.6 and 10.10 are running on the ports 5432. Are these ports on the host machine or are they on the two individual containers. This is a common question asked and it will be nioce if you could please clarify. Otherwise it is a great lecture series. I have subscribed and liked!! :)
Hi ,Thank you for posting the tutorial, it helping me a lot and learning new concepts. thank you so much again.
i have query on docker image i.e. In tutorial,at one point explained Docker Image package the all the dependencies. what is mean to it dependencies of what kind could you please elaborate bit more clear.
Thank you
Looks like you can't docker run postgre without a password for the superuser. Anyone else seeing the same? Can't seem to workaround that.
This is the message I get when I try to docker run postgre:
Error: Database is uninitialized and superuser password is not specified.
You must specify POSTGRES_PASSWORD for the superuser. Use "-e POSTGRES_PASSWORD=password" to set it in "docker run". You may also use POSTGRES_HOST_AUTH_METHOD=trust to allow all connections without a password. This is *not* recommended. See PostgreSQL documentation about "trust": www.postgresql.org/docs/current/auth-trust.html
I realize this is by design (according to the postgre image developers). I've tried setting the -e parameters on the docker run line but the message still persists and I'm not able to start the container. Anyone else figured out a workaround?
@@masonfoley1276 you should put -e parameter in this order: docker run -e POSTGRES_PASSWORD=*** postgres:9.6
@@masonfoley1276 Run this: docker run -e POSTGRES_PASSWORD=datpassword postgres
I tried this with maven latest image. It pulled everything but the image is not running and I am not able to locate docker/library/maven section on my ubuntu linux machine
How is it possible to run 2 containers from different image versions on same port, I agree internally they can use same port but how it is exposed to hostmachines?
@Nana
you should learn the internals of this. these layers are actually the layers of unionfs file system. each line in a dockerfile creates a new layer. an image is a set of read only unionfs layers, compressed. when a container is created, a new writable unionfs layer is added on top of read only layers that come from image. container process isolation is done by linux cgroups and namespaces etc.
Congratulations
hi Nana iam unable to docker push run hello-world to docker repository to my hub can u tell me how to do that nana plz
Intro music is too loud, but invaluable tutorial, thanks
VERY GOOD NANA
#ROYALNIL
Informative. Thank you.
Appreciate the support SV. Please don't forget to share to your friends. More tutorials to come. 😉