blocks|key|4140045|text|命名卷将存储在docker的文件夹(/var/lib/docker)中。如果要在特定的主机文件夹中创建卷，请使用具有以下语法的主机卷：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4140046|docker+run+-v+/home/ubuntu/data/app-data:/app-data+my-image|code-block|syntax|javascript|4140047|或者来自您的撰写文件：|4140048|version:+'2'
services:
++++mongo:
++++++++container_name:+"CaseBook-db"
++++++++restart:+always
++++++++image:+mongo:3.2.7
++++++++ports:
++++++++++++-+"27017"
++++++++volumes:
++++++++++++-+/home/ubuntu/data/db:/data/db
++++++++labels:
++++++++++++-+"ENVIRONMENT_TYPE=meteor"

++++app:
++++++++container_name:+"CaseBook-app"
++++++++restart:+always
++++++++image:+"meteor/casebook"
++++++++build:+.
++++++++depends_on:
++++++++++++-+mongo
++++++++environment:
++++++++++++-+MONGO_URL=mongodb://mongo:27017/CaseBook
++++++++ports:
++++++++++++-+"80:3000"
++++++++volumes:
++++++++++++-+/home/ubuntu/data/uploads:/Meteor-CaseBook-Container/.uploads
++++++++labels:
++++++++++++-+"ENVIRONMENT_TYPE=meteor"|4140049|对于主机卷，映像中卷的任何内容都将被主机文件夹的确切内容覆盖，包括主机文件夹的UID。空的主机文件夹不会像空的命名卷那样从映像中初始化。UID映射往往是使用主机卷时最困难的部分。|4140050|4140051|编辑:根据下面的注释，如果您需要一个命名卷作为主机卷，docker's+plugin+list上列出了一个local+persist+volume+plugin。安装该插件后，您可以创建指向主机文件夹的卷，其功能是即使在删除命名卷之后，主机目录也会保留下来。插件中的示例用法包括：|offset|length|4140052|docker+volume+create+-d+local-persist+-o+mountpoint=/data/images+--name=images
docker+run+-d+-v+images:/path/to/images/on/one/+one
docker+run+-d+-v+images:/path/to/images/on/two/+two|4140053|它们还包括一个包含以下卷示例的v2合成文件：|4140054|volumes:
++data:
++++driver:+local-persist
++++driver_opts:
++++++mountpoint:+/data/local-persist/data|4140055|4140056|我在过去一个月中了解到的另一个选项是使用本地卷驱动程序的挂载选项来手动创建绑定挂载。这类似于docker中的主机卷，但有以下区别：|4140057|4140058|如果目录不存在，则尝试启动具有指向绑定挂载的命名卷的容器将失败。对于主机卷，docker会将其初始化为根拥有的空目录。|unordered-list-item|4140059|如果该目录为空，则命名卷将使用装载位置的映像内容初始化绑定装载，包括文件和目录所有权/权限。使用主机卷时，不需要初始化主机目录内容。|4140060|4140061|要创建命名卷作为绑定挂载，可以使用以下命令提前创建：|4140062|docker+volume+create+--driver+local+\
++--opt+type=none+\
++--opt+device=/home/user/test+\
++--opt+o=bind+\
++test_vol|4140063|在docker+run命令中，可以使用--mount完成此操作|style|CODE|4140064|docker+run+-it+--rm+\
++++--mount+type=volume,dst=/container/path,volume-driver=local,volume-opt=type=none,volume-opt=o=bind,volume-opt=device=/home/user/test+\
++++foo|4140065|或者在合成文件中，您可以使用以下命令创建命名卷：|4140066|volumes:
++data:
++++driver:+local
++++driver_opts:
++++++type:+none
++++++o:+bind+
++++++device:+/home/user/test+|4140067|如果您需要命名卷的功能，我更喜欢使用命名卷与本地驱动程序一起使用，而不是本地持久化第三方驱动程序。|4140068|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/extend/legacy_plugins/|1|https://github.com/CWSpear/local-persist^0|0|0|0|0|0|0|R|K|0|1H|R|1|0|0|0|0|0|0|0|0|0|0|0|0|1|A|J|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|20|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|21|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|23|8|@]|9|@$P|24|Q|25|1|26]|$P|27|Q|28|1|29]]|A|$]]|$1|R|3|S|5|D|7|2A|8|@]|9|@]|A|$E|F]]|$1|T|3|U|5|6|7|2B|8|@]|9|@]|A|$]]|$1|V|3|W|5|D|7|2C|8|@]|9|@]|A|$E|F]]|$1|X|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2E|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|11|3|12|5|13|7|2G|8|@]|9|@]|A|$]]|$1|14|3|15|5|13|7|2H|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|2J|8|@]|9|@]|A|$]]|$1|19|3|1A|5|D|7|2K|8|@]|9|@]|A|$E|F]]|$1|1B|3|1C|5|6|7|2L|8|@$P|2M|Q|2N|1D|1E]|$P|2O|Q|2P|1D|1E]]|9|@]|A|$]]|$1|1F|3|1G|5|D|7|2Q|8|@]|9|@]|A|$E|F]]|$1|1H|3|1I|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|D|7|2S|8|@]|9|@]|A|$E|F]]|$1|1L|3|1M|5|6|7|2T|8|@]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|2U|8|@]|9|@]|A|$]]]|1O|$1P|$5|1Q|1R|1S|A|$1T|1U]]|1V|$5|1Q|1R|1S|A|$1T|1W]]]]

Named volumes will be stored inside docker's folder (/var/lib/docker). If you want to create a volume in a specific host folder, use a host volume with the following syntax:

<pre><code>docker run -v /home/ubuntu/data/app-data:/app-data my-image
</code></pre>

Or from your compose file:

<pre><code>version: '2'
services:
 mongo:
 container_name: "CaseBook-db"
 restart: always
 image: mongo:3.2.7
 ports:
 - "27017"
 volumes:
 - /home/ubuntu/data/db:/data/db
 labels:
 - "ENVIRONMENT_TYPE=meteor"

 app:
 container_name: "CaseBook-app"
 restart: always
 image: "meteor/casebook"
 build: .
 depends_on:
 - mongo
 environment:
 - MONGO_URL=mongodb://mongo:27017/CaseBook
 ports:
 - "80:3000"
 volumes:
 - /home/ubuntu/data/uploads:/Meteor-CaseBook-Container/.uploads
 labels:
 - "ENVIRONMENT_TYPE=meteor"
</code></pre>

With host volumes, any contents of the volume inside the image will be overlaid with the exact contents of the host folder, including UID's of the host folder. An empty host folder is not initialized from the image the way an empty named volume is. UID mappings tend to be the most difficult part of using a host volume.

<hr>

Edit: from the comments below, if you need a named volume that acts as a host volume, there is a <a href="https://github.com/CWSpear/local-persist" rel="noreferrer">local persist volume plugin</a> that's listed on <a href="https://docs.docker.com/engine/extend/legacy_plugins/" rel="noreferrer">docker's plugin list</a>. After installing the plugin, you can create volumes that point to host folders, with the feature that even after removing the named volume, the host directory is left behind. Sample usage from the plugin includes:

<pre><code>docker volume create -d local-persist -o mountpoint=/data/images --name=images
docker run -d -v images:/path/to/images/on/one/ one
docker run -d -v images:/path/to/images/on/two/ two
</code></pre>

They also include a v2 compose file with the following volume example:

<pre><code>volumes:
 data:
 driver: local-persist
 driver_opts:
 mountpoint: /data/local-persist/data
</code></pre>

<hr>

One additional option that I've been made aware of in the past month is to use the local volume driver's mount options to manually create a bind mount. This is similar to a host volume in docker with the following differences:

<ul>
<li>If the directory doesn't exist, trying to start a container with a named volume pointing to a bind mount will fail. With host volumes, docker will initialize it to an empty directory owned by root.</li>
<li>If the directory is empty, a named volume will initialize the bind mount with the contents of the image at the mount location, including file and directory ownership/permissions. With a host volume, there is no initialization of the host directory contents.</li>
</ul>

To create a named volume as a bind mount, you can create it in advance with:

<pre><code>docker volume create --driver local \
 --opt type=none \
 --opt device=/home/user/test \
 --opt o=bind \
 test_vol
</code></pre>

From a <code>docker run</code> command, this can be done with <code>--mount</code>:

<pre><code>docker run -it --rm \
 --mount type=volume,dst=/container/path,volume-driver=local,volume-opt=type=none,volume-opt=o=bind,volume-opt=device=/home/user/test \
 foo
</code></pre>

Or in a compose file, you can create the named volume with:

<pre><code>volumes:
 data:
 driver: local
 driver_opts:
 type: none
 o: bind 
 device: /home/user/test 
</code></pre>

My preference would be to use the named volume with the local driver instead of the local-persist 3rd party driver if you need the named volume features.

blocks|key|4140089|text|内置本地驱动程序的另一种方式：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4140090|docker+volume+create+--opt+type=none+--opt+device=/home/ubuntu/data/+--opt+o=bind+data_db|code-block|syntax|javascript|4140091|(此示例使用以下示例:在docker-compose中将data_db声明为外部命名卷，并将/home/ubuntu/data/声明为主机上的文件夹)|4140092|entityMap^0|0|2|0|0|S|7|1A|I|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

Another way with build-in driver local: 

<pre><code>docker volume create --opt type=none --opt device=/home/ubuntu/data/ --opt o=bind data_db
</code></pre>

(This use DimonVersace example with: data_db declared as external named volume in docker-compose and /home/ubuntu/data/ as the folder on the host machine)

On my <code>Ubuntu EC2</code> I host an application using docker containers. <code>db</code> data and <code>upload</code> data is being stored in volumes <code>CaseBook-data-db</code> and <code>CaseBook-data-uploads</code> which are being created with this commands:

<pre><code>docker volume create --name=CaseBook-data-db
docker volume create --name=CaseBook-data-uploads
</code></pre>

Volumes being attached through <code>docker-compose</code> file:

<pre><code>version: '2'
services:
 mongo:
 container_name: "CaseBook-db"
 restart: always
 image: mongo:3.2.7
 ports:
 - "27017"
 volumes:
 - data_db:/data/db
 labels:
 - "ENVIRONMENT_TYPE=meteor"

 app:
 container_name: "CaseBook-app"
 restart: always
 image: "meteor/casebook"
 build: .
 depends_on:
 - mongo
 environment:
 - MONGO_URL=mongodb://mongo:27017/CaseBook
 ports:
 - "80:3000"
 volumes:
 - data_uploads:/Meteor-CaseBook-Container/.uploads
 labels:
 - "ENVIRONMENT_TYPE=meteor"
volumes:
 data_db:
 external:
 name: CaseBook-data-db
 data_uploads:
 external:
 name: CaseBook-data-uploads
</code></pre>

I need to store those docker volumes in different folder(for example <code>/home/ubuntu/data/</code>) of the host machine. How to change docker storage folder for volumes? Or there is a better way in doing this? Thank you in advance.

Docker: change folder where to store docker volumes

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的Ubuntu EC2上，我使用停靠容器托管一个应用程序。db数据和upload数据存储在使用以下命令创建的卷CaseBook-data-db和CaseBook-data-uploads中：docker volume create --name=CaseBook-data-dbdocker volume creat...

问Docker:更改存储docker卷的文件夹
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker:更改存储docker卷的文件夹EN