This is based on the road strength of the host ,ĭocker run -d -name demo -v vol2:/usr/share/nginx/html:ro nginx # The colon is preceded by a volume, Instead of an arbitrary path docker exec -it demo bash ls cd /usr/share/nginx/html/īut by default, No, -v There is no read-write permission. Ls docker ps docker exec -it demo bash cd /usr/share/nginx/html Write the name before the colon, Write the data path in the container laterĭocker run -d -name demo -v vol1:/usr/share/nginx/html nginxĭocker exec -it demo bash ls cd /usr/share/nginx/htmlĭocker run -d -name demo -v /data1:/usr/share/nginx/html nginx ĭocker run -d -name demo -v vol1:/var/lib/registry registry ĭocker volume ls docker run -d -name demo registryĭocker The management volume can only support the mounting of directories, Cannot support file mounting. docker hostory nginx:latestĭocker volume ls # If any, Clean up volume docker volume pruneīecause the container does not define the mounting of volumes, So the container did not create a volume, therefore docker The engine won't create for you when it's running. If you point to the existing directory in the container when mounting, The original data will be copied to volume in. The data volume directory created by default is /var/lib/docker/volumes in. ĭocker managed volume You don't have to specify mount Source ,docker Automatically create data volume directories for containers. īind mount Must specify host File system Lu Jin, Limited portability. Ls touch file2 # It's not allowed to write in this. Ro Indicates read-only, In addition to being able to attach directories, You can also attach files docker run -rm -it -v /data1./data1 -v /data2:/data2:ro -v /etc//dvd.repo:/dvd.repo:ro busybox The container here is well-defined, Running here is an application, By default, the application will be written to the road strength under this container, If you want to save the data to the host, You should connect the previous road strength to this road strength. The above write file is actually written to the file of the host server1 and server2ĭocker network prune # Release the unused objects docker ps docker rm -f demo1ĭocker run -rm -it -v /data1:/data1 busybox Use -v Option specifies the road stiffness, Format :,： It used to be the absolute road strength of the host computer, Behind is the road strength in the container, If there is a direct hitch, However, there is no way to create. Use intuitive and efficient, Easy to understand. Is to transfer the directory or file on the host mount Into the container. ĭocker There are two types of volumes :bind mind, docker managed volume Mount To the host, Bypass the hierarchical file system, Same performance as host disk, The container remains after deletion, Local disks only, Cannot migrate with container. Docker Hierarchical file system, Poor performance, The life cycle is the same as container
0 kommentar(er)
