{"id":20984,"date":"2015-06-19T08:48:58","date_gmt":"2015-06-19T07:48:58","guid":{"rendered":"https:\/\/www.inovex.de\/\/?p=583"},"modified":"2026-03-17T07:59:03","modified_gmt":"2026-03-17T06:59:03","slug":"docker-an-introduction-to-easy-containerization","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/docker-an-introduction-to-easy-containerization\/","title":{"rendered":"Docker: An introduction to easy containerization"},"content":{"rendered":"

Docker is a lightweight container virtualization platform,\u00a0a container\u00a0being\u00a0an isolated Linux system which runs on an single Linux host. Docker helps the user to package a system into an image which can be shipped to a Docker registry to provide it to other systems which are running the Docker client. Read on to find out about the advantages of this architecture.<\/p>\n

There are two major benefits when using Docker or containers in general.\u00a0First: less overhead compared to a full-blown hypervisor\u00a0and\u00a0second: a tool to package your software and dependencies into an image that runs\u00a0(nearly) anywhere.<\/p>\n

Actually, container technology is pretty old. It has been present\u00a0in\u00a0the solaris zones (2005, v1.0), can be found in cgroups (2007, initial release), LXC (2013, v1.0) and now\u00a0Docker (2014, v1.0). I would bet that the container roots are even deeper and older. Still, Docker made it easy for everyone to build and run their own containers. With the container hype in 2014 even big companies jumped on\u00a0the bandwagon\u00a0and built solutions to integrate containers or even built \u201cnew\u201c operating systems with the aim to run containers in an optimal way.<\/p>\n

\n

<\/p>\n<\/div>