• docker对已经启动的容器添加目录映射(挂载目录)


    1. 背景

    在自己安装sharding-proxy时,使用docker run -v的方式启动时,只挂载了/opt/shardingsphere-proxy/conf/opt/shardingsphere-proxy/ext-lib这两个目录,忘记挂载/opt/shardingsphere-proxy/logs日志目录,导致每次查看都得要进入容器内部去查看,很是麻烦,于是考虑如何在不删除容器重新启动部署的情况下进行新目录的映射与挂载

    2. 开始新增挂载目录

    1. 查看容器存放目录
    [root@iZ2zedqr9yeos47fg4uor5Z proxy-a]# docker info | grep 'Root'
     Docker Root Dir: /var/lib/docker
    [root@iZ2zedqr9yeos47fg4uor5Z proxy-a]#
    
    • 1
    • 2
    • 3
    1. 查看要新增挂载的容器id
    [root@iZ2zedqr9yeos47fg4uor5Z proxy-a]# docker ps
    CONTAINER ID   IMAGE                               COMMAND                  CREATED       STATUS          PORTS                               NAMES
    6f5f3c195304   apache/shardingsphere-proxy:5.1.1   "/bin/sh -c '${LOCAL…"   4 days ago    Up 9 minutes    0.0.0.0:3321->3307/tcp              server-proxy-a
    
    • 1
    • 2
    • 3
    1. 进入要新增文件夹挂载的目录
    [root@iZ2zedqr9yeos47fg4uor5Z proxy-a]# docker ps
    CONTAINER ID   IMAGE                               COMMAND                  CREATED       STATUS          PORTS                               NAMES
    6f5f3c195304   apache/shardingsphere-proxy:5.1.1   "/bin/sh -c '${LOCAL…"   4 days ago    Up 11 minutes   0.0.0.0:3321->3307/tcp              server-proxy-a
    [root@iZ2zedqr9yeos47fg4uor5Z proxy-a]# cd /var/lib/docker/containers/
    [root@iZ2zedqr9yeos47fg4uor5Z containers]# ll
    total 64
    drwx------ 4 root root 4096 Nov  7 14:20 1d0c21204385f60fa8859b0ff199569988218e449155634470cfb14ff2ceebf9
    drwx------ 4 root root 4096 Nov  7 14:20 21a5f8b6e68ee09f8f80381c536b38abec1b8dcb81c69f1c50caeb95e8ebb35f
    drwx------ 4 root root 4096 Nov  7 14:20 28242c9fd16bd610880d42a773e078221a0d34b1c779935fc0c8609a1b63666a
    drwx------ 4 root root 4096 Nov  7 14:22 2bc290c8e158229fdc5291a3ea53c5721f5becd39c8cb47cb2f826f6349ac778
    drwx------ 4 root root 4096 Nov  7 14:20 2fc0e1b1031abe6b1871332b971ccdc40185b7441e94ba3c266f51d2d4728412
    drwx------ 4 root root 4096 Nov  7 14:20 3124c345f129a3c542423c68061c6ded5b41a649b25991125c8e81da7b010e7e
    drwx------ 4 root root 4096 Nov  7 14:20 4a1e699a3711b92918f711d7ab021a5ac62bab1b8353ed321337c6f94ac50533
    drwx------ 4 root root 4096 Nov  7 14:20 4cdc6456250a922e60f3394b26064be0541f04a0c34825c6487e73ed7979705a
    drwx------ 4 root root 4096 Nov  7 14:20 53d710c37c08b9c2ab0c84fea2059d067bbcbc38f22aa2e654e1c62758b1df44
    drwx------ 4 root root 4096 Nov  7 14:41 6f5f3c1953044043672723cdf4f3725c500e77a54e07cd0a4759371c04c0cfa1
    drwx------ 4 root root 4096 Nov  7 14:20 73cc941fd394d42b8cbdc8fd7a50fc098b5d56c0323e5b9a786703d21a102d33
    drwx------ 4 root root 4096 Nov  7 14:35 8dc6124199b0ef6afbc9d2b542c5a46c8767e7daafd52bfedd53a83491e17db0
    drwx------ 4 root root 4096 Nov  7 14:20 9c554d94d5eb6c2c6015994b52ae3f3c31d182dde189d86427840b4a1c5d6477
    drwx------ 4 root root 4096 Nov  7 14:20 a073fcd724623a98168564707dccfb9562d94d89c0882ad2fd92798a2137be0d
    drwx------ 4 root root 4096 Nov  7 14:21 b1191679d1ecea73a74f44ee74b33281fbcccc942307630db02f2cb9e86869d0
    drwx------ 4 root root 4096 Nov  7 14:20 eb30519b4804f9ca3c708260e885f99d693332af4a162a956952b601332fed97
    [root@iZ2zedqr9yeos47fg4uor5Z containers]# cd 6f5f3c1953044043672723cdf4f3725c500e77a54e07cd0a4759371c04c0cfa1/
    [root@iZ2zedqr9yeos47fg4uor5Z 6f5f3c1953044043672723cdf4f3725c500e77a54e07cd0a4759371c04c0cfa1]# ll
    total 488
    -rw-r----- 1 root root 461990 Nov  7 14:41 6f5f3c1953044043672723cdf4f3725c500e77a54e07cd0a4759371c04c0cfa1-json.log
    drwx------ 2 root root   4096 Nov  2 22:29 checkpoints
    -rw------- 1 root root   4041 Nov  7 14:41 config.v2.json
    -rw-r--r-- 1 root root   1705 Nov  7 14:41 hostconfig.json
    -rw-r--r-- 1 root root     13 Nov  7 14:41 hostname
    -rw-r--r-- 1 root root    174 Nov  7 14:41 hosts
    drwx------ 2 root root   4096 Nov  2 22:29 mounts
    -rw-r--r-- 1 root root    149 Nov  7 14:41 resolv.conf
    -rw-r--r-- 1 root root     71 Nov  7 14:41 resolv.conf.hash
    [root@iZ2zedqr9yeos47fg4uor5Z 6f5f3c1953044043672723cdf4f3725c500e77a54e07cd0a4759371c04c0cfa1]#
    
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    • 21
    • 22
    • 23
    • 24
    • 25
    • 26
    • 27
    • 28
    • 29
    • 30
    • 31
    • 32
    • 33
    • 34
    • 35

    我们将要修改的文件就是config.v2.jsonhostconfig.json

    1. 关闭容器、关闭docker
    systemctl stop docker
    
    • 1
    1. 修改config.v2.json

    说明:想要将容器中的/opt/shardingsphere-proxy/logs目录映射到宿主机的/atguigu/server/proxy-a/logs目录下。
    config.v2.json文件中找到MountPoints,添加如下/opt/shardingsphere-proxy/logs的映射即可(这里如果前面还有内容的话,注意逗号)

    {
        ......
    	
    	"MountPoints": {
    		......,
    		"/opt/shardingsphere-proxy/logs": {
    			"Source": "/atguigu/server/proxy-a/logs",
    			"Destination": "/opt/shardingsphere-proxy/logs",
    			"RW": true,
    			"Name": "",
    			"Driver": "",
    			"Type": "bind",
    			"Propagation": "rprivate",
    			"Spec": {
    				"Type": "bind",
    				"Source": "/atguigu/server/proxy-a/logs",
    				"Target": "/opt/shardingsphere-proxy/logs"
    			},
    			"SkipMountpointCreation": false
    		}
    	},
    	
    	......
    	
    }
    
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    • 21
    • 22
    • 23
    • 24
    • 25
    1. 修改hostconfig.json
      说明:Binds中添加内容"/atguigu/server/proxy-a/logs:/opt/shardingsphere-proxy/logs"
    {
    	"Binds": [
    		......,
    		"/atguigu/server/proxy-a/logs:/opt/shardingsphere-proxy/logs"
    	],
    	
    	......
    	
    }
    
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    1. 重启docker与容器
    systemctl start docker
    
    • 1
    docker start 容器id
    
    • 1
    1. 进行目录验证

    目录成功映射出来,查看日志就不用每次很麻烦的进入容器内部查看了

    [root@iZ2zedqr9yeos47fg4uor5Z logs]# pwd
    /atguigu/server/proxy-a/logs
    [root@iZ2zedqr9yeos47fg4uor5Z logs]# ll
    total 36
    -rw-r--r-- 1 root root 36421 Nov  7 14:41 stdout.log
    -rw-r--r-- 1 root root     0 Nov  7 14:41 xa_tx1.log
    -rw-r--r-- 1 root root     0 Nov  7 14:41 xa_tx.lck
    [root@iZ2zedqr9yeos47fg4uor5Z logs]#
    
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8

    3. 注意

    1. config.v2.jsonhostconfig.json文件修改之前,需要关闭docker与容器!如果先修改了这两个文件,再关闭docker,这两个文件中的内容会被重置掉,导致新增的目录映射失效 (自己在这里折腾了很久才发现的!
    2. config.v2.jsonhostconfig.json文件vi命令打开后,并非格式化后的json,这里可以通过:%!python3 -m json.tool命令将其进行格式化,方便查看
  • 相关阅读:
    互斥锁、条件变量、信号量以及适用场景
    Windows编程技术之运行单一实例
    基于SSM框架流浪猫救援网站的设计与实现毕业设计源码201502
    为何电脑从 C 盘开始? A、B 盘去哪了
    Spring 中的 Bean
    触摸一体机广告机开发板_MTK联发科平台超小型安卓主板方案
    鸿鹄工程项目管理系统em Spring Cloud+Spring Boot+前后端分离构建工程项目管理系统
    transformer系列4---transformer结构计算量统计
    2023年全网最全的软件测试八股文,稳进大厂(含答案)
    Hadoop2——Hadoop程序实现
  • 原文地址:https://blog.csdn.net/qq_39198749/article/details/127731024