After long months of studying, I finally understand docker concept. I hope all Tech teachers know how to teach like the way you do. Even five year old can understand this and when it comes to docker, I am a five-year-old myself!!!! Thank you so much!!!
Anyone who is wanting to learn Docker should watch this guys videos. While longer, it will be worth it. He seems to have a better understanding of Docker than most devs. Including pulling docker images to compare and custom build them, which is what you should do. Grab a slimmed down base image and add specifically what you need. @takacsmark I see your using zsh. I hope you have some aliases and custom functions made for your common docker commands. If not, make some :) I have this for cleaning dangling: alias docker.cleanimage="docker images --filter dangling=true -q | xargs docker rmi" as well as this one: alias docker.cleancontainer="docker ps -a -q | xargs docker rm" Thanks and keep up the videos!
Forgot, here are my aliases for zsh. I just switched to Oh-My-Zsh, so it isn't huge, but has some handy dandy ones: gist.github.com/WadeShuler/bd873db7cd9051f2c0d231f3f7f3e0a8
Wow thank you so much. I don't spend much time on such aliases, I do my hacking after work and time is so precious. Plus I'm really enjoying the sound of Cherry MX blue switches. :)
Hi, thanks for the helpful stream, one question, if you can customize your image manually by interactively logining into the base container, installing needed software, and use docker commit to build an image, why would you still use Dockfile? I understand Dockfile is more portable than an image, but in a corporate environment, wouldn't it be easier for you to give a readily built image to another person vs handing over the Dockerfile, and he/she has to build it from scratch? thanks.
I suggest working with the Dockerfile. If you use the Dockerfile, it is clear how the image is built. You can share the Dockerfile with others so that they can work with it, too. You'll also share the image that you build with the Dockerfile on Docker Hub or other Docker Registry. If you use Docker commit, you are often also not sure yourself how you built the final state of the image. Changing it in the future would be a pain if you build an image with docker commit. If you want to upgrade one of your installed components in an image built with commit, you would probably remove the old version and install a new one, you never now what side effects this would have. It's always better to start clean and execute steps that always produce the same results. Especially if you work in a team on a commercial assignment. I'd always go with the Dockerfile, I don't use docker commit at all.
Thanks for your reply, I am also looking at containerized our current SFTP server, in which we have 100+ users in the /etc/passwd and /etc/shadow file, putting it into docker container would mean that each time we add/remove a user, we'd need to rebuild the container for it to stay persistently , I understand you can map volumes to the host for the user home dirs to stay in persistent state, what about users credentials in passwd/shadow file, can I map them to the host volume too? thanks
Went through two of your tutorials .. it's more of a "what is dockerfile" then a tutorial. .. given my 1 hr into these videos and you have only explained From Copy Run and not to forget the most important one Maintainer... Expected more from these tutorial
Hi, Could you please provide an example of adding content to bash_profile or bashrc from within a docker file? I need to pass proxy params and aliases which i use frequently.
Wouldn't it be better to add your params as environment variables with ENV? You can add those to the Dockerfile, but it's better to pass at runtem, you can use environment variables in docker run on with docker-compose, maybe this would be a better solution than writing to bash profile.
What does the "alpine" part represent? It's only 5mb isn't it? Is it safe for use on Production? Thanks for the great tutorial by the way... very helpful!
It's an honor to see this high quality content comes from a Hungarian guy.
Hi Róbert, thanks for connecting! I wish you happy learning!
At last, a docker tutorial everyone understands!
Your method to explain and structure step-by-step is champion. It worth every minute. Tks
After long months of studying, I finally understand docker concept. I hope all Tech teachers know how to teach like the way you do. Even five year old can understand this and when it comes to docker, I am a five-year-old myself!!!! Thank you so much!!!
Anyone who is wanting to learn Docker should watch this guys videos. While longer, it will be worth it. He seems to have a better understanding of Docker than most devs. Including pulling docker images to compare and custom build them, which is what you should do. Grab a slimmed down base image and add specifically what you need.
@takacsmark I see your using zsh. I hope you have some aliases and custom functions made for your common docker commands. If not, make some :)
I have this for cleaning dangling:
alias docker.cleanimage="docker images --filter dangling=true -q | xargs docker rmi"
as well as this one:
alias docker.cleancontainer="docker ps -a -q | xargs docker rm"
Thanks and keep up the videos!
Forgot, here are my aliases for zsh. I just switched to Oh-My-Zsh, so it isn't huge, but has some handy dandy ones: gist.github.com/WadeShuler/bd873db7cd9051f2c0d231f3f7f3e0a8
Wow thank you so much. I don't spend much time on such aliases, I do my hacking after work and time is so precious. Plus I'm really enjoying the sound of Cherry MX blue switches. :)
What a great tutorial
Amazing hands on explanation, Grateful for your work.
This tutorial is helpful to understand how to go with building a Dockerfile from scratch. Thank you.
Really very nice for person having basic knowledge of Linux command. Good in-depth knowledge...
Your tutorial are great , its really very nice to listen your speech , that makes the things very easy to understand. :)
Excellent tutorial. Thank you.
Please prepare tutorials on Docker Volume and Networking
Nice explanation. Keep it coming!
excellent! thanks! Brilliant best practice tips...
Hi I need to setup a reverse nginx proxy for docker container.how to do it?
Thank you for this useful tutorial : )
You are welcome. :)
Hi, thanks for the helpful stream, one question, if you can customize your image manually by interactively logining into the base container, installing needed software, and use docker commit to build an image, why would you still use Dockfile? I understand Dockfile is more portable than an image, but in a corporate environment, wouldn't it be easier for you to give a readily built image to another person vs handing over the Dockerfile, and he/she has to build it from scratch? thanks.
I suggest working with the Dockerfile. If you use the Dockerfile, it is clear how the image is built. You can share the Dockerfile with others so that they can work with it, too. You'll also share the image that you build with the Dockerfile on Docker Hub or other Docker Registry. If you use Docker commit, you are often also not sure yourself how you built the final state of the image. Changing it in the future would be a pain if you build an image with docker commit. If you want to upgrade one of your installed components in an image built with commit, you would probably remove the old version and install a new one, you never now what side effects this would have. It's always better to start clean and execute steps that always produce the same results. Especially if you work in a team on a commercial assignment. I'd always go with the Dockerfile, I don't use docker commit at all.
Thanks for your reply, I am also looking at containerized our current SFTP server, in which we have 100+ users in the /etc/passwd and /etc/shadow file, putting it into docker container would mean that each time we add/remove a user, we'd need to rebuild the container for it to stay persistently , I understand you can map volumes to the host for the user home dirs to stay in persistent state, what about users credentials in passwd/shadow file, can I map them to the host volume too? thanks
You are Amazing, Thank you!
Went through two of your tutorials .. it's more of a "what is dockerfile" then a tutorial. .. given my 1 hr into these videos and you have only explained From Copy Run and not to forget the most important one Maintainer... Expected more from these tutorial
Hi, Could you please provide an example of adding content to bash_profile or bashrc from within a docker file? I need to pass proxy params and aliases which i use frequently.
Wouldn't it be better to add your params as environment variables with ENV? You can add those to the Dockerfile, but it's better to pass at runtem, you can use environment variables in docker run on with docker-compose, maybe this would be a better solution than writing to bash profile.
What does the "alpine" part represent? It's only 5mb isn't it? Is it safe for use on Production? Thanks for the great tutorial by the way... very helpful!
Alpine is a linux distribution famous for its small footprint.
Dangling docker images: Do you know the command "docker prune"? It does the job more easily...
excepte it is not a docker command.
very helpfull BOSS
Please make more videos!
just wow and love
Thank you!
Thank you to discover me Alpine. Really convenient Linux distribution.
And for other things of course
Thanks :)
I'm on ADSL conneciton so u can imagine how slow was been this moment 14:16. I managed to take a shower.
Now I can leave my virtual machines behind