# 启动容器➜ docker_start_test docker run -itd --name docker_run_test 4cbf48630b46 ping 127.0.0.1d6278f537113122d4ccbe00950790750215c5a09002bcbd1ef6f9e660fc9eaac➜ docker_start_test docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESd6278f537113 4cbf48630b46 "ping 127.0.0.1" 3 seconds ago Up 2 seconds docker_run_test# 进容器增加文件➜ docker_start_test docker exec -it docker_run_test /bin/shsh-4.2# pwd/sh-4.2# touch testsh-4.2# exitexit# 重启容器➜ docker_start_test docker stop docker_run_testdocker_run_test➜ docker_start_test docker ps -a | grep docker_run_testd6278f537113 4cbf48630b46 "ping 127.0.0.1" About a minute ago Exited (137) 12 seconds ago docker_run_test# 进去查看文件是否存在➜ docker_start_test docker start docker_run_testdocker_run_test➜ docker_start_test docker exec -ti docker_run_test /bin/shsh-4.2# lsanaconda-post.log bin dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys test tmp usr var# stop / rm掉容器➜ docker_start_test docker stop docker_run_testdocker_run_test➜ docker_start_test docker ps -a | grep docker_rund6278f537113 4cbf48630b46 "ping 127.0.0.1" 7 minutes ago Exited (137) 13 seconds ago docker_run_test➜ docker_start_test docker rm d6278f537113d6278f537113# 启动新的同名容器➜ docker_start_test docker run -itd --name docker_run_test 4cbf48630b46 ping 127.0.0.199a6f5df0a86e4c07abf184e322a23e4fbec89ff354691459cdac8fcd8687ba3# 进入容器验证➜ docker_start_test docker exec -ti docker_run_test /bin/shsh-4.2# lsanaconda-post.log bin dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr varsh-4.2# ls testls: cannot access test: No such file or directorydocker run的说明
从官网看到,start命令的作用是:
Start one or more stopped containers
emmm,挺直白,没什么可说的
PS
其实最好的办法,就是将容器的存储目录挂载出来…另外,一般来讲似乎数据库服务不应该使用容器启动
总结
IEPL专线/IPLC面向企业客户,提供优质点对点国际专线服务。支撑客户语音、数据和视频会议等日常办公应用。国际专线建基于国际标准和独享平台,可保证客户电路独立分隔,安全无忧。
以上所述是小编给大家介绍的docker run启动的容器挂掉了数据怎么办,希望对大家有所帮助!