Docker-0005(Docker容器数据卷)

一、什么是容器数据卷

        Docker将运用与运行的环境打包形成容器运行 ,运行可以伴随着容器,但是我们对数据的要求希望是持久化的,而且有时候我们希望容器之间有可能共享数据。

        Docker容器产生的数据,如果不通过docker commit生成新的镜像,使得数据做为镜像的一部分保存下来,那么当容器删除后,数据自然也就没有了。因此为了能保存数据在docker中我们使用卷。

        卷就是目录或文件,存在于一个或多个容器中,由docker挂载到容器,但不属于联合文件系统,因此能够绕过Union File System提供一些用于持续存储或共享数据的特性:
 
        卷的设计目的就是数据的持久化,完全独立于容器的生存周期,因此Docker不会在容器删除时删除其挂载的数据卷。

二、容器数据卷特点

        1:数据卷可在容器之间共享或重用数据

        2:卷中的更改可以直接生效

        3:数据卷中的更改不会包含在镜像的更新中

        4:数据卷的生命周期一直持续到没有容器使用它为止

三、容器内添加容器数据卷(直接命令添加)

 docker run -it -v /宿主机绝对路径目录:/容器内目录 镜像名

        我们假设需要按照如下命令开始配置容器数据卷,实现宿主机和Docker容器的数据共享

 docker run -it -v /Docker_Share_Master:/Docker_Share_Continer centos

        我们先使用原始的启动容器命令,看看是宿主机和Docker容器内否分别有 /Docker_Share_Master、/Docker_Share_Continer,如下图

        图片说明:

                1:启动centos容器

                2:查看centos容器中目录

                3:没有/Docker_Share_Continer目录

                4:退出centos容器,回到宿主机

                5:查看宿主机目录,宿主机没有 /Docker_Share_Master目录

        接下来我们使用容器数据卷启动容器,执行下面命令

 docker run -it -v /Docker_Share_Master:/Docker_Share_Continer centos

        如下图所示,宿主机和容器中分别有了 /Docker_Share_Master、/Docker_Share_Continer

         接下来,我们无论是在宿主机在 /Docker_Share_Master下做修改还是在容器中/Docker_Share_Continer下做修改,两端都会同时刷新。而且我们关闭Docker容器后,在宿主机修改 /Docker_Share_Master下内容,再重新启动关闭的容器后,融汇会把宿主机 /Docker_Share_Master下的内容同步至自己的/Docker_Share_Continer中。

         我们再查看容器信息,执行下面命令

 docker ps
 docker inspect ${docker ps查询出当前正在运行的容器ID}

        我们可以得到如下回显信息

[
    {
        "Id": "b754744f29062abf9f1af8856746c205e5ea0b6432c69cdcfc065d7e8d26dbd3",
        "Created": "2020-12-09T14:48:19.778265906Z",
        "Path": "/bin/bash",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 2340,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2020-12-09T14:48:20.280371083Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:0d120b6ccaa8c5e149176798b3501d4dd1885f961922497cd0abef155c869566",
        "ResolvConfPath": "/var/lib/docker/containers/b754744f29062abf9f1af8856746c205e5ea0b6432c69cdcfc065d7e8d26dbd3/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/b754744f29062abf9f1af8856746c205e5ea0b6432c69cdcfc065d7e8d26dbd3/hostname",
        "HostsPath": "/var/lib/docker/containers/b754744f29062abf9f1af8856746c205e5ea0b6432c69cdcfc065d7e8d26dbd3/hosts",
        "LogPath": "/var/lib/docker/containers/b754744f29062abf9f1af8856746c205e5ea0b6432c69cdcfc065d7e8d26dbd3/b754744f29062abf9f1af8856746c205e5ea0b6432c69cdcfc065d7e8d26dbd3-json.log",
        "Name": "/zealous_murdock",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/Docker_Share_Master:/Docker_Share_Continer"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "default",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "Capabilities": null,
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": [],
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "KernelMemory": 0,
            "KernelMemoryTCP": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": false,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/dd86608d366ead6debd28097c8c7763a490323d2de0d266f9139870c6587a769-init/diff:/var/lib/docker/overlay2/7d39e92b1af62942ea487e5d1123adc66526a43e389a21f218ff196f084732d7/diff",
                "MergedDir": "/var/lib/docker/overlay2/dd86608d366ead6debd28097c8c7763a490323d2de0d266f9139870c6587a769/merged",
                "UpperDir": "/var/lib/docker/overlay2/dd86608d366ead6debd28097c8c7763a490323d2de0d266f9139870c6587a769/diff",
                "WorkDir": "/var/lib/docker/overlay2/dd86608d366ead6debd28097c8c7763a490323d2de0d266f9139870c6587a769/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [
            {
                "Type": "bind",
                "Source": "/Docker_Share_Master",
                "Destination": "/Docker_Share_Continer",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "b754744f2906",
            "Domainname": "",
            "User": "",
            "AttachStdin": true,
            "AttachStdout": true,
            "AttachStderr": true,
            "Tty": true,
            "OpenStdin": true,
            "StdinOnce": true,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "/bin/bash"
            ],
            "Image": "centos",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {
                "org.label-schema.build-date": "20200809",
                "org.label-schema.license": "GPLv2",
                "org.label-schema.name": "CentOS Base Image",
                "org.label-schema.schema-version": "1.0",
                "org.label-schema.vendor": "CentOS"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "1ce01550089195b3c0e6f48142da54b6bf971e1810ac33a4731164d6a22bade1",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/1ce015500891",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "a2c5304a4ba499344e974e2c3bed5a99f55199e2147817cac1f9d388888fb8d6",
            "Gateway": "172.17.0.1",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "172.17.0.2",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:02",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "0e28162d0a3f500025e8bea5bdacde0fa9a543e32a95a2cee15039228304658c",
                    "EndpointID": "a2c5304a4ba499344e974e2c3bed5a99f55199e2147817cac1f9d388888fb8d6",
                    "Gateway": "172.17.0.1",
                    "IPAddress": "172.17.0.2",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:02",
                    "DriverOpts": null
                }
            }
        }
    }
]

        我们可以从中看到几行很重要的信息

        容器内添加容器数据卷,加写保护 

 docker run -it -v /宿主机绝对路径目录:/容器内目录:ro 镜像名

         这样共享的数据目录只有宿主机能修改,容器内只有读权限 

四、容器内添加容器数据卷(DockerFile添加)

        注意:关于DockerFile详细内容我们后续说道,这里只讲述在通过编辑DockerFile在容器中添加数据卷

        在宿主机上执行下面三条指令

mkdir DockerFile
cd DockerFile/
vim CentOsDockerFile

        在 CentOsDockerFile中编辑如下内容

# volume test
FROM centos
# 在当前镜像中生成两个容器内的数据卷目录/dataVolumeContainer1和/dataVolumeContainer2
VOLUME ["/dataVolumeContainer1","/dataVolumeContainer2"]
CMD echo "finished,--------success1"
CMD /bin/bash

 

        执行下面命令将CentOsDockerFile构建为一个新的Docker镜像

docker build -f CentOsDockerFile -t my-self-centos .

        执行下面命令查看我们创建的镜像

docker images

        执行下面命令运行我们创建的镜像

docker run -it affba109f987 /bin/bash

        执行完毕直接进入了镜像,查看镜像中已经有了 /dataVolumeContainer1和/dataVolumeContainer2,如下图所示

       通过上述步骤,我们已经在容器内建了两个容器数据卷,那么我们在宿主机上的数据卷路径呢?我们在宿主机上执行下面命令查看一下。

 docker ps
 docker inspect ${docker ps查询出当前正在运行的容器ID}

         执行完毕有如下关键内容截取

        通过图中的结果我们可以发现,Docker会在宿主机中默认给不同容器数据卷生成对应的宿主机目录。 

 

 

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值