Configuration management mode and device based on Docker

Abstract

The invention provides a configuration management mode based on a Docker. The configuration management mode is applied in a Docker operating environment which comprises multiple containers. The configuration management mode comprises the steps that configuration requirements of the containers in the Docker operating environment are acquired; underlying system commands corresponding to the configuration requirements are determined; the containers in the Docker operating environment are configured and managed according to the configuration requirements and by calling the underlying system commands. According to the embodiment of the configuration management mode, the problem that an original configuration management mode of the Docker on the virtualized containers in the Docker is incomplete is solved; by executing the underlying system commands, the multiple containers can be rapidly configured to meet the requirements of an actual generating environment; for example, the CPU usage rate of each container can be reasonably limited, IP addresses of the containers in the network configuration can be flexibly limited, usable independent disk space can be configured and distributed for each container, and therefore various actual configuration requirements of an administrator on the multiple containers in the Docker operating environment can be met.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular, the present invention relates to a configuration management method and device based on Docker. Background technique [0002] Docker is an open source application container engine, which aims to provide an automated deployment solution for applications. It can quickly create a container container (lightweight virtual machine) on a Linux system and deploy and run applications. It is very convenient to automate the installation, deployment and upgrade of applications easily. Docker virtualizes multiple containers, and each container is isolated from each other without an interface. It can separate each other's production environment and development environment without affecting each other, and each container has its own independent namespace namespace, including: PID process , MNT file system, NET network, IPC, UTS (UNIX Time-sharing System, UNIX Time-sharing System), etc. ...

AI Technical Summary

Problems solved by technology

[0003] The existing native Docker has an imperfect configuration management method for its internal virtualized containers, and cannot configure and manage multiple containers in a simple and quick way

For example, it is impossible to limit the CPU usage of each container; the network segment that can be assigned an IP address in the network configuration is fixed, and it is impossible to assign a customized IP address to each container based on user needs; it is impossible to configure for each container free independent disk space

Images