docker is a lightweight containerization system applications with open source. Currently there are several hundreds of Linux distributions. Each type of Linux distribution has its own peculiarities in the installation and configuration of applications:
- Differences in the procedure of installing packages (apt-get, yum, dnf, …).
- Differences batch database (desired package can be omitted).
- Package name, version and installation mechanism may vary.
- Packages are built with various options and add-ons.
- The configuration files are located in different places.
All this creates serious problems when transferring a running application from one Linux distribution to another.
Docker solves this problem by creating a file system image that includes in addition to the application itself all the required libraries and configuration files. Thus setting the image of docker-apps built for one type of distribution (e.g. Ubuntu), You can based on it to start the container running the application on a different distribution (e.g. ALTLinux).
Unlike other virtualization systems (e.g. Virtuozzo/OpenVZ) docker applications of the same type of distribution is through the use of cascade-combined (layered) mount use the same libraries, configuration files, underlying distribution. This makes optimum use of the file system to reduce the amount of resources consumed by kontejnerov and reduce the time of its launch. This same mechanism allows you to design your own images by extending (inheritance) of existing images, thus creating a tree of images of the distributions.
The undoubted advantage of docker is the presence of hundreds of official and unofficial up to half a million public images on hub-portal. Finding the right way app You can install it on your computer and run the application containers does not care about the incompatibility of Linux distributions.
In addition, You can expanding the received image to create a custom image app adding your configuration files and extra packages.
For example, if You need to run Your MPI program, You can download image MPI compiler from CentOS:
# docker pull nersc/centos-mpi
To create your own podobrat, using the instructions given on the page image and run Your MPI application with different parameters on different Linux distributions.
The technology for creating docker images based on existing You can examine on the page Build your own images.
- kafnevod/altlinux.p7-apache2 - image of the Apache2 server
- flexberry/altlinux.p7-apache2-mono184.108.40.206 image Apache2/Mono4 servers.
These images use the certified distribution library ALTLinux C7 and, if necessary, can be used instead of the described in this document images kafnevod/altlinux.p8-apache2, flexberry/altlinux.p8-apache2-mono220.127.116.11 collected on the distribution ALTLinux/BaseALT P8.
When you run container You can pass it various parameters to bind TCP ports application container to various ports on the HOST system, mount the directory HOST system in the subdirectories of the container.
All these mechanisms allow you to run within a single OS:
- multiple containers with a single application of one версии;
- several containers of versions of different versions of the same приложения;
- applications conflicting TCP ports or file системе;
- swarm (swarm) container that supports some сервис;
The image WEB server Apache2: kafnevod/altlinux.p8-apache2
Install the image and run the container
Let’s say You need to run Ember-app under WEB-server Apache2. You can simply download the image server for distribution ALTLinux P8:
# docker pull kafnevod/altlinux.p8-apache2
The launch container is performed with the command:
# docker run -d -p 80:80 --name=apache2 kafnevod/altlinux.p8-apache2
The container starts in daemon mode (-d) with name (–name) apache2 and bind a port (-p) 80 of the container to port 80 of the HOST system.
To verify that the container, run the command:
# docker ps -f name=apache2
The command will show a line like:
CONTAINER_ID IMAGE COMMAND CREATED STATUS PORTS NAMES 688acc21b881 kafnevod/altlinux.p8-apache2 httpd2 5 seconds Up 4 seconds 0.0.0.0:80->80/tcp apache2
The IMAGE column contains the name of the image container. Column NAMES - the container name. Column CONTAINER ID - ID (UID) of the container. Column list of the PORTS attached ports container ports on the HOST system. The STATUS column - status of the container (start up, restart, …). Column CREATED - time since the start of the container. The COMMAND column is the name and parameters of the root process of the container.
Using the docker exec command You can start the process in the working container, for example, the pstree command (process tree):
# docker exec apache2 pstree
Command shows the current process tree container:
You can also run bash interpretator
# docker exec -it apache2 bash
and interactively work within the container. For example, to dynamically view the log files apache2-server with the command:
# tail -f /var/log/httpd2/*log
Check the operation of the container
To test the operation of the container type in the browser URL: http://localhost/. The browser will display the text: It works!
Here and below we consider the case when the container is launched on the user’s computer. If You launch a container on a remote server, replace the server name in the URL from localhost to the IP address of the server or the domain name under which the server works. For testing purposes You can specify one or more domains of the server in the /etc/hosts file.
If Your browser runs through a proxy server, describe the test addresses and server domains in the field “do not use proxy server” window proxy server settings of the browser.
If You are in a container started the above command logs view tail, it will print lines like:
==> /var/log/httpd2/access_log <== 172.18.0.1 - - [26/Dec/2016:10:25:17 +0000] "GET / HTTP/1.1" 200 45
Running your own virtual website within container
The description file of the virtual sites on apache2 server container is in the file /conf/vhosts.conf image. To start their own virtual site (for example demo) You must:
- Place the tree of the website in a separate directory (e.g. /var/www/vhosts/demo/) HOST system. Let this be a simple test page /var/www/vhosts/demo/index.html:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <title>Тестовая demo-страница для проверки работоспособности виртуального хоста в контейнере kafnevod/altlinux.p8-apache2</title> </head> <body> <b><i>Виртуальный хост demo.local контейнера kafnevod/altlinux.p8-apache2 работает!</i></b> </body> </html>
- Describe the configuration of that virtual host in the configuration file vhosts.conf a separate directory. For example, /etc/docker/apache2/conf/vhosts.conf:
NameVirtualHost *:80 <VirtualHost *:80> DocumentRoot "/var/www/vhosts/demo/" ServerName demo.local ErrorLog "/var/log/httpd2/demo_log" CustomLog "/var/log/httpd2/demo_log" common </VirtualHost>
- To remove a running container, if You have it running:
# docker rm -f apache2
- Run a new container with the command:
# docker run -d \ -p 80:80 \ --name=apache2Virt \ -v /etc/docker/apache2/conf/:/conf/ \ -v /var/www/vhosts/:/var/www/vhosts/ \ kafnevod/altlinux.p8-apache2
Options-v mount configuration directory /conf/ directory and virtual sites /var/www/vhosts/ container to the /etc/docker/apache2/conf/ /var/www/vhosts/ HOST-system.
- Describe virtual domain in /etc/hosts file:
127.0.0.1 demo.local ... localhost
If You launch a container on a remote server, instead of the 127.0.0.1 address in /etc/hosts file of the host where You launch the browser you have to add the line:
If You run a virtual website for external access, instead of editing /etc/hosts file Zaregistriruytes domain (e.g. demo.ics.perm.ru) with your ISP domain and specify it in the description of the configuration file /etc/docker/apache2/conf/vhosts.conf.
Check the operation of the virtual site in the container
To check the operation of the virtual website type in your browser’s URL: http://demo.local/. The browser will display the text: Wirtualny host demo.local container kafnevod/altlinux.p8-apache2 works!_
Server image Mono/.NET applications flexberry/altlinux.p8-apache2-mono18.104.22.168
Install the image and run the container
To run mono applications download flexberry image/altlinux.p8-apache2-mono22.214.171.124:
# docker pull flexberry/altlinux.p8-apache2-mono126.96.36.199
Please note - as the way flexberry/altlinux.p8-apache2-mono188.8.131.52 is an extension of the image kafnevod/altlinux.p8-apache2, then the layers of the file system that are already present in the parent image to the child image is not downloaded.
6ed0c8c1348d: Already exists 3083620832f3: Already exists 03daa402b3d6: Already exists b867bce38065: Pulling fs layer
When you start the container a child of the image he uses layers of the file system of the parent image. The test image contains the virtual site accessible on TCP port 880. To check the test website, run a container loaded image:
# docker run -d -p 880:880 --name=apache2Mono flexberry/altlinux.p8-apache2-mono184.108.40.206
Check the operation of the container
Check the status of the container:
docker ps -a -f name=apache2Mono CONTAINER_ID IMAGE COMMAND CREATED STATUS PORTS NAMES 38c7e2a7a8aa flexberry/altlinux.p8-apache2-mono220.127.116.11 httpd2 2minutes ago Up 2minutes 80/tcp, 0.0.0.0:880->880/tcp apache2Mono
Type in the browser the URL of the virtual test site with Mono-app http://localhost:880/. In the browser to display the result of the test mono-app - key Click me!.
Start your own virtual Mono/.NET site within the container
Start your own virtual Mono/.NET site is equivalent to running virtual site Apache2-server:
- Place trees site in a separate directory (for example /var/www/vhosts/myMonoApp/) HOST system.
- Copy the virtual host configuration file of Mono application from a running container:
docker cp apache2Mono:/conf/vhosts.conf /etc/docker/apache2/conf/vhosts.conf
- Add the configuration of Your virtual host in the copied configuration file: /etc/docker/apache2/conf/vhosts.conf using the template:
Listen 881 NameVirtualHost *:881 <VirtualHost *:881> ServerName myMonoApp.local MonoServerPath test.local "/usr/bin/mod-mono-server4" MonoDebug myMonoApp.local true MonoSetEnv myMonoApp.local MONO_IOMAP=all MonoApplications myMonoApp.local "/:/var/www/vhosts/myMonoApp" AddDefaultCharset utf-8 <Location "/"> Allow from all Order allow,deny MonoSetServerAlias myMonoApp SetHandler mono #SetOutputFilter DEFLATE </Location> ErrorLog /var/log/httpd2/myMonoApp_error_log LogLevel debug CustomLog /var/log/httpd2/myMonoApp_access_log common </VirtualHost>
Replace, if necessary, the 881 port to the port number you are going to use Your website, putting in the port in the-p flag when running the container. Domain myMonoApp.local to Your application domain name myMonoApp the name of Your mono application.
Restart the container :
# docker rm -f apache2Mono # docker run -d \ -p 880:880 \ -p 881:881 \ --name=apache2MonoVirt \ -v /etc/docker/apache2/conf/:/conf/ \ -v /var/www/vhosts/:/var/www/vhosts/ \ flexberry/altlinux.p8-apache2-mono18.104.22.168
Check the operation of the virtual site in the container Mono/.NET applications
Refer the browser to the root page of the virtual website URL: http://localhost:881/.
After the completion of the container it remains in the list and can be found in the list of containers the ps command with the-a flag:
# docker ps -a
If the container is named (at startup, use the flag –name=iracontainer), then re-run the container with the same name will cause an error.
To remove a completed container-use the rm command:
# docker rm ID_контейнера_или_его_имя
Intensive process of starting the containers (usually during testing) the list of stopped containers can be quite large and cleaning this list may create some temporary problems. If You do not plan to restart the container after its completion, or plan to repeatedly run the named container, use the –rm flag after an argument run start command. In this case, the container after automatically deleted from the list of completed containers. For example
docker run -d -p 80:80 --rm --name=apache2 kafnevod/altlinux.p8-apache2
If You need to automatically restart a container after it (emergency) stop and automatically start the container after restarting the system, use the –restart flag=unless-stopped argument after the run command that starts the container. For example:
docker run -d -p 80:80 --restart=unless-stopped --name=apache2 kafnevod/altlinux.p8-apache2
docker for Windows
Run Docker for Windews Windews 8 and Server 2012 in a virtual machine Virtualbox.
In Windeos 10 Professional, and Windows Server 2016 appeared natina support Docker.
Run Linux containers in Windows Server 2016 and Windows 10 Professional
When you run Linux containers in HyperV create a virtual machine of Linux, boot Linux Moby and runs all Linux containers.
Run Windows containers on Windows Server 2016 and Windows 10 Professional
Supported two startup mode of Windows-containers:
- the Windows Server container - the container runs within the HOST OS and uses the kernel and shared resources of the HOST system.
- Hyper-V container container runs in a separate virtual machine on Hyper-V.
Links to materials for the study
Lectures, courses, presentations, videos
Docker for Linux
- Docker Video Tutorials
- Docker YouTube Channel
- 5 must-watch videos Docker
- Video reports meet up with Docker
- Docker in the Bank. Video lectures by Alexander Tarasov from Alfa Bank
- 350 useful resources, books and tools for working with Docker
- Get started with Docker
- The Docker commands
- Docker run reference
- Series Play-With:
- Play with Docker;
- Classroom Play with Docker;
- Play with Kubernetes;
- Play with Kubernetes Classroom;
Docker for Windows
- WINDOWS CONTAINERS AND DOCKER
- WORKING WITH CONTAINERS AND DOCKER IN WINDOWS
- Docker: Windows and Linux containers on a single machine