Shulou(Shulou.com)05/31 Report--

This article mainly shows you the "Portainer visualization panel how to install", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "Portainer visualization panel how to install" this article.

Visualization

Portainer (not the best choice, use this first)

Docker run-d-p 8088 9000\

>-- restart=always-v / var/run/docker.sock:/var/run/docker.sock-- privileged=true portainer/portainer

Rancher (used for CI/CD continuous integration / continuous deployment)

What is portainer?

Docker graphical interface management tools! Provide a background panel for us to operate!

Docker run-d-p 8088 9000\

>-- restart=always-v / var/run/docker.sock:/var/run/docker.sock-- privileged=true portainer/portainer

Access test: public network: 8088 http://ip:8088/

Set the password and select the local

Note: there is a prompt on this page to mount the local / var/run/docker.socker connection to the / var/run/docker.socker in the container. Therefore, the mount file must be developed at startup.

Enter the panel after entering:

Visual panels are not usually used, just test and play by yourself.

Docker Mirror explains what a mirror is

An image is a lightweight, executable, independent software package that packages the software runtime environment and the software developed based on the runtime environment. It contains everything needed to run a software, including code, runtime libraries, environment variables, and configuration files.

All applications, directly package docker image, you can run directly!

How to get an image:

Download from remote warehouse

Friend copy

Make your own mirror DockerFile

Principle of Docker image loading

UnionFS (federated file system)

This is what we see layer by layer when we download!

UnionFS (federated file system): the Union file system (UnionFS) is a hierarchical, lightweight, and high-performance file system that allows file system modifications to be superimposed layer by layer as a commit, while different directories can be mounted to the same virtual file system (unite several directories into a single virtual filesystem). The Union file system is the foundation of Docker mirroring. Images can be inherited through layering. Based on the basic image (without a parent image), you can create a variety of specific application images.

Features: multiple file systems are loaded at a time, but from the outside, only one file system can be seen. Joint loading will stack the file systems of each layer, so that the final file system will contain all the underlying files and directories.

Principle of Docker image loading

The image of docker is actually made up of a layer-by-layer file system, the file system UnionFS at this level.

Bootfs (boot file system) mainly consists of bootloader and kernel,bootloader. The boot load kernel,Linux loads the bootfs file system when it starts, and at the bottom of the Docker image is bootfs. This layer is the same as our typical Linux/Unix system, including the boot loader and kernel. When the boot is loaded, the entire kernel is in memory, the right to use the memory has been transferred from the bootfs to the kernel, and the system will unload the bootfs.

Rootfs (root file system), on top of bootfs. It contains standard directories and files such as / dev, / proc, / bin, / etc in a typical Linux system. Rootfs is a variety of different operating system distributions, such as Ubuntu,Centos and so on.

Usually we install several gigabytes of CentOS into the virtual machine, why is it only 200m here in Docker?

Think about it: why do Docker images adopt such a hierarchical structure?

I think the biggest advantage is the sharing of resources! For example, if multiple images are built from the same Base image, the host only needs to keep one base image on disk and only one base image needs to be loaded in memory, so that all containers can be served, and each layer of the image can be shared.

The way to view image layering is through the docker image inspect command!

[root@dockertest ~] # docker image inspect redis:latest

[

/ /.

"RootFS": {

"Type": "layers"

"Layers": [

"sha256:cb42413394c4059335228c137fe884ff3ab8946a014014309676c25e3ac86864"

"sha256:8e14cb7841faede6e42ab797f915c329c22f3b39026f8338c4c75de26e5d4e82"

"sha256:1450b8f0019c829e638ab5c1f3c2674d117517669e41dd2d0409a668e0807e96"

"sha256:f927192cc30cb53065dc266f78ff12dc06651d6eb84088e82be2d98ac47d42a0"

"sha256:a24a292d018421783c491bc72f6601908cb844b17427bac92f0a22f5fd809665"

"sha256:3480f9cdd491225670e9899786128ffe47054b0a5d54c48f6b10623d2f340632"

]

}

"Metadata": {

"LastTagTime": "0001-01-01T00:00:00Z"

}

}

]

Understand:

All Docker mirrors are actually the same as the base mirror layer, and when you modify or add new content, a new mirror layer is created on the current mirror layer.

To take a simple example, if you create a new image based on Ubuntu Linux 16.04, this is the first layer of the new image; if you add the Python package to that image, a second mirror layer will be created above the underlying mirror layer; if you continue to add security patches, a third mirror layer will be created.

The mirror currently contains three mirror layers, as shown in the following figure (this is just a simple example for demonstration).

The mirror layer in the image above is slightly different from the one in the previous image, and the main purpose is to facilitate the presentation of the file.

The following figure shows a slightly complex image with only six files externally, because file 7 in the top layer is a newer version of file 6.

In this case, the files in the upper mirror layer overwrite the files in the underlying mirror layer. This causes the updated version of the file to be added to the mirror as a new mirror layer.

Docker implements the mirror layer stack through the storage engine (the new version uses the snapshot mechanism), and ensures that multiple mirror layers are exposed as a unified file system.

The storage engines available on Linux are AUFS, Overlay2, Device Mapper, Btrfs, and ZFS. As the name implies, each storage engine is based on the corresponding file system or block device technology in Linux, and each storage engine has its own unique performance characteristics.

Docker supports only one storage engine, windowfilter, on Windows, which implements tiering and CoW on top of the NTFS file system.

The following shows the same three-layer images as shown by the system, all of which are stacked and merged to provide a unified view.

Characteristics

Docker images are read-only, and when the container starts, a new writable layer is loaded on top of the image!

This layer is what we usually call the container layer, under the container is called the mirror layer!

How to submit an image of yourself

Commit Mirror

The docker commit submission container becomes a new copy

The # command is similar to git.

Docker commit-m = "submitted description information"-a = "author" container id target image name: [TAG]

Actual combat test

# 1. Start a default tomcat

# 2. It is found that there is no webapps application for this default tomcat, because there are no files under the default webapps of the official image!

# 3. I copied in the basic files myself.

# 4. Submit the container we have operated to a new image through commit! We will use the modified image later, and this is one of our own modified images.

If you want to save the state of the current container, you can submit it through commit and get an image, just like a snapshot of a virtual machine!

The above is all the contents of the article "how to install the Portainer Visualization Panel". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.