Docker review today

Hi!

Welcome back! 🙂

I’m glad to see that you are visiting my blog and follow some topics.

The topics are not only IT Tech related but also some personal point of view about way of work and quality of what we do and how to improve ourself.

Why Docker?

Today the topic is Docker.
Docker is a very interesting and friendly system that allows you to save resources and your nervous system.
Why the Nervous system – well… the moment when we provide an application/source code/working system to someone who is not using our computers.
“It’s not working!… But it works on my Computer!” -> its gone for good.
No matter what Operation System you use – Linux, MacOS, Windows… it will work for you as it should work in the way that the author wants you to see it.

I really enjoy using Docker as it gives me the opportunity to build stuff and break them to pieces. Even if something went wrong – it’s not gonna ruin my day and my system as I can just rebuild my work.
Even better if you use Git or GitHub or even other version control application/system.
No need of crazy big backups, endless archives and server to keep your test Docker images. While you are exploring Docker – you can use free options to store your stuff online on official hub – hub.docker.io (this is not an Ad. – I’m sharing my personal experience and my advise to you)

Practice Over Theory

Today I realised that Docker is not a small system or system you can’t find a reason to use it over the legacy ways of work.
Its more flexible and easy to understand while using it. Don’t get lost in endless tutorials. you can learn more by doing.

So today I’ve went through topics like
-How it works
-Looks logical and simple to understand but it requires practical experience to MAKE IT simple to understand 🙂
-New mechanism that I will need to understand better -> FEEL FREE TO CONTACT ME TO DISCUSS THAT MECHANISM if you understand it
-Docker volume mounting/bind , create, load , manage… use… not big deal when you get it but again -> PRACTICE, PRACTICE and again PRACTICE is the key.
-SO its good to be able to store the data in a volume with the idea to not loose it and also to protect it with a password to be more secure
Like: docker run -d -v /opt/data:/var/lib/mysql –name mysql-db -e MYSQL_ROOT_PASSWORD=db_pass123 mysql
… no worries, it makes sense when you use it in a project.
-Docker Network -> this is what I could say: Amazing!!! That topic can be FUN for people who wants to play around with some kind of home servers and apps hosted on home server but without exposing your home network to the world. Lots of nice tricks to stay safe.

For now Docker is a nice topic to discuss and gather some experience not only from doing but also there are lots of Youtubers who share projects and that they use Docker and Docker swarm and Docker-compose… some resources that deserves comments and ideas.

Oh… I’ve almost forgot… Docker Registry – well… its a topic that needs some attention but maybe in special cases. Special cases as when we work in a professional environment we often will be deep into the private area of the projects that we will/are working on. And there are more points to cover on this topic.
That’s why we learn, we grow and we share.

Reminder: Privacy is important not only for our job but also from personal perspective!


Thanks for reading!
If you’d like, just say “Hi” on LinkedIn or at zhivko@zlefterov.com — I’d love to know you stopped by.

Leave a Comment

Your email address will not be published. Required fields are marked *