Deploying on a new server is really easy.You can get it to run on any Linux distro, given that Docker is installed (Ubuntu, Amazon Linux, вЂ¦).The best things about having a web app in containers, in my opinion, are: Only containers start faster and have less resource overhead. That sounds an awful lot like VMs, right? Yup. The process running inside a container thinks itвЂ™s the only one and only sees a barebones Linux distro the stuff which is described in the image. It should only access exactly the resources it is allowed to (storage, CPU, memory), and does not know there is anything else on the machine. Imagine youвЂ™d like run a command isolated from everything else on the system. Here are 6 Docker basics, explained in a brief and practical manner: Containers A firm understanding of those will make it easier for you to ask the right questions,ДЄnd will help you navigate the sea of Docker-stuff without feeling lost.

But why? WhatвЂ™s the advantage of using Docker? Will it make my life easier even if the project is small and not that hard to deploy at the moment?Д«efore trying to judge the usefulness, you should get to know the most important elements and tools around the Docker ecosystem when getting started.

ThereвЂ™s lots of projects using it and all kinds of people talking about it. After doing a bit of googling to get an overview of the things people do with it, youвЂ™re probably a bit overwhelmed. The idea is to test it out and see how it fits into your current tools. YouвЂ™re here because you want to use Docker for a small project. 6 Docker Basics You Should Completely Grasp When Getting Started

Docker run image basics