blocks|key|27659|text|每个容器都有自己的文件系统，独立于主机文件系统。如果使用-v标志运行容器，则可以挂载卷，以便主机和容器看到相同的数据(与docker+run+-v+hostFolder:containerFolder中一样)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|27660|您打印的第一个输出描述了这样一个已挂载的卷(因此挂载)，其中将/var/lib/docker/volumes/fac362...80535/_data+(主机)挂载到/webapp+(容器)。|27661|我假设您没有使用-v，因此该文件夹没有挂载，只能在容器文件系统中访问，您可以在/var/lib/docker/volumes/blog_postgres-data/_data中找到它。如果您删除容器(docker+-rm)，此数据将被删除，因此挂载该文件夹可能是一个好主意。|27662|关于在哪里可以从windows访问这些数据的问题。据我所知，docker+for+windows在windows10中使用bash子系统。我会尝试运行bash+for+windows10并转到那个文件夹，或者了解如何在windows10中访问linux文件夹。查看此page以获取有关windows10中linux子系统的常见问题。|27663|更新:您还可以使用docker+cp在主机和容器之间复制文件。|27664|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/commandline/wsl/faq|1|https://docs.docker.com/engine/reference/commandline/cp/^0|S|2|1O|14|0|V|18|2B|7|0|8|2|13|1C|2S|A|0|3P|4|0|0|9|9|1|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|L|3|M|5|6|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|N|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|W]]]]

Each container has its own filesystem which is independent from the host filesystem. If you run your container with the <code>-v</code> flag you can mount volumes so that the host and container see the same data (as in <code>docker run -v hostFolder:containerFolder</code>).
The first output you printed describes such a mounted volume (hence mounts) where <code>/var/lib/docker/volumes/fac362...80535/_data</code> (host) is mounted to <code>/webapp</code> (container).
I assume you did not use <code>-v</code> hence the folder is not mounted and only accessible in the container filesystem which you can find in <code>/var/lib/docker/volumes/blog_postgres-data/_data</code>. This data will be deleted if you remove the container (<code>docker -rm</code>) so it might be a good idea to mount the folder.
As to the question where you can access this data from windows. As far as I know, docker for windows uses the bash subsystem in Windows 10. I would try to run bash for windows10 and go to that folder or find out how to access the linux folders from windows 10. Check this <a href="https://msdn.microsoft.com/en-us/commandline/wsl/faq" rel="nofollow noreferrer">page</a> for a FAQ on the linux subsystem in windows 10.
Update: You can also use <a href="https://docs.docker.com/engine/reference/commandline/cp/" rel="nofollow noreferrer">docker cp</a> to copy files between host and container.

blocks|key|29107|text|挂载任何基于NTFS的目录对我的目的不起作用(据我所知，至少对于Redis和CouchDB，MongoDB也是如此)：NTFS权限不允许运行在容器中的这类数据库进行必要的访问。以下是在HyperV上使用命名卷的设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29108|以下方法在服务中启动ssh服务器，并使用docker-compse进行设置，以便它自动启动，并在主机和容器之间使用公钥加密进行授权。这样，数据可以通过scp或sftp上传/下载。|29109|下面是webapp+%2B+mongodb的完整docker-compose.yml，以及一些关于如何使用ssh服务的文档：|29110|version:+'3'
services:
++foo:
++++build:+.
++++image:+localhost.localdomain/${repository_name}:${tag}
++++container_name:+${container_name}
++++ports:
++++++-+"3333:3333"
++++links:
++++++-+mongodb-foo
++++depends_on:
++++++-+mongodb-foo
++++++-+sshd
++++volumes:
++++++-+"${host_log_directory}:/var/log/app"

++mongodb-foo:
++++container_name:+mongodb-${repository_name}
++++image:+"mongo:3.4-jessie"
++++volumes:
++++++-+mongodata-foo:/data/db
++++expose:
++++++-+'27017'

++#since+mongo+data+on+Windows+only+works+within+HyperV+virtual+disk+(as+of+2019-4-3),+the+following+allows+upload/download+of+mongo+data
++#setup:+you+need+to+copy+your+~/.ssh/id_rsa.pub+into+$DOCKER_DATA_DIR/.ssh/id_rsa.pub,+then+run+this+service+again
++#download+(all+mongo+data):+scp+-r+-P+2222+user@localhost:/data/mongodb+[target-dir+within+/c/]
++#upload+(all+mongo+data):+scp+-r+-P+2222+[source-dir+within+/c/]+user@localhost:/data/mongodb
++sshd:
++++image:+maltyxx/sshd
++++volumes:
++++++++-+mongodata-foo:/data/mongodb
++++++++-+$DOCKER_DATA_DIR/.ssh/id_rsa.pub:/home/user/.ssh/keys/id_rsa.pub:ro
++++ports:
++++++++-+"2222:22"
++++command:+user::1001

#please+note:+using+a+named+volume+like+this+for+mongo+is+necessary+on+Windows+rather+than+mounting+an+NTFS+directory.
#mongodb+(and+probably+most+other+databases)+are+not+compatible+with+windows+native+data+directories+due+ot+permissions+issues.
#this+means+that+there+is+no+direct+access+to+this+data,+it+needs+to+be+dumped+elsewhere+if+you+want+to+reimport+something.
#it+will+however+be+persisted+as+long+as+you+don't+delete+the+HyperV+virtual+drive+that+docker+host+is+using.
#on+Linux+and+Docker+for+Mac+it+is+not+an+issue,+named+volumes+are+directly+accessible+from+host.
volumes:
++mongodata-foo:|code-block|syntax|javascript|29111|这是不相关的，但对于一个完整的工作示例，在任何docker-compose调用之前，需要运行以下脚本：|29112|#!/usr/bin/env+bash
set+-o+errexit
set+-o+pipefail
set+-o+nounset

working_directory="$(pwd)"
host_repo_dir="${working_directory}"
repository_name="$(basename+${working_directory})"
branch_name="$(git+rev-parse+--abbrev-ref+HEAD)"
container_name="${repository_name}-${branch_name}"
host_log_directory="${DOCKER_DATA_DIR}/log/${repository_name}"
tag="${branch_name}"

export+host_repo_dir
export+repository_name
export+container_name
export+tag
export+host_log_directory|29113|sshd更新：请注意，您现在也可以只使用docker+cp，因此可能不再需要上面列出的sshd容器，除非您需要远程访问在主机下的容器中运行的文件系统。|offset|length|style|BOLD|29114|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/commandline/cp/^0|0|0|0|0|0|0|1O|F|K|9|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|17|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|18|8|@$Q|19|R|1A|S|T]]|9|@$Q|1B|R|1C|1|1D]]|A|$]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

Mounting any NTFS based directories did not work for my purpose (MongoDB - as far as I'm aware it is also the case for Redis and CouchDB at least): NTFS permissions did not allow necessary access for such DBs running in containers. The following is a setup with named volumes on HyperV.

The following approach starts an ssh server within a service, setup with docker-compse such that it automatically starts up and uses public key encryption between host and container for authorization. This way, data can be uploaded/downloaded via scp or sftp.

The full docker-compose.yml for a webapp + mongodb is below, together with some documentation on how to use ssh service: 

<pre><code>version: '3'
services:
 foo:
 build: .
 image: localhost.localdomain/${repository_name}:${tag}
 container_name: ${container_name}
 ports:
 - "3333:3333"
 links:
 - mongodb-foo
 depends_on:
 - mongodb-foo
 - sshd
 volumes:
 - "${host_log_directory}:/var/log/app"

 mongodb-foo:
 container_name: mongodb-${repository_name}
 image: "mongo:3.4-jessie"
 volumes:
 - mongodata-foo:/data/db
 expose:
 - '27017'

 #since mongo data on Windows only works within HyperV virtual disk (as of 2019-4-3), the following allows upload/download of mongo data
 #setup: you need to copy your ~/.ssh/id_rsa.pub into $DOCKER_DATA_DIR/.ssh/id_rsa.pub, then run this service again
 #download (all mongo data): scp -r -P 2222 user@localhost:/data/mongodb [target-dir within /c/]
 #upload (all mongo data): scp -r -P 2222 [source-dir within /c/] user@localhost:/data/mongodb
 sshd:
 image: maltyxx/sshd
 volumes:
 - mongodata-foo:/data/mongodb
 - $DOCKER_DATA_DIR/.ssh/id_rsa.pub:/home/user/.ssh/keys/id_rsa.pub:ro
 ports:
 - "2222:22"
 command: user::1001

#please note: using a named volume like this for mongo is necessary on Windows rather than mounting an NTFS directory.
#mongodb (and probably most other databases) are not compatible with windows native data directories due ot permissions issues.
#this means that there is no direct access to this data, it needs to be dumped elsewhere if you want to reimport something.
#it will however be persisted as long as you don't delete the HyperV virtual drive that docker host is using.
#on Linux and Docker for Mac it is not an issue, named volumes are directly accessible from host.
volumes:
 mongodata-foo:
</code></pre>

this is unrelated, but for a fully working example, before any docker-compose call the following script needs to be run: 

<pre><code>#!/usr/bin/env bash
set -o errexit
set -o pipefail
set -o nounset

working_directory="$(pwd)"
host_repo_dir="${working_directory}"
repository_name="$(basename ${working_directory})"
branch_name="$(git rev-parse --abbrev-ref HEAD)"
container_name="${repository_name}-${branch_name}"
host_log_directory="${DOCKER_DATA_DIR}/log/${repository_name}"
tag="${branch_name}"

export host_repo_dir
export repository_name
export container_name
export tag
export host_log_directory
</code></pre>

Update: Please note that you can also just use <a href="https://docs.docker.com/engine/reference/commandline/cp/" rel="nofollow noreferrer">docker cp</a> nowadays, so the sshd container outlined above is probably not necessary anymore, except if you need remote access to the file system running in a container under a Windows host.

blocks|key|27885|text|在windows主机上运行基于linux的容器时，实际卷将存储在linux虚拟机中，并且在主机的文件系统上不可用，否则windows将在windows+=>+C:\ProgramData\Docker\+volumes+\上运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|27886|此外，docker+inspect+<container_id>还将列出容器配置，请在装载部分下查看有关持久层的更多详细信息。|offset|length|style|CODE|27887|更新:不适用于在WSL上运行的Docker。|27888|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/docker-for-windows/wsl/^0|0|3|T|0|8|3|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

When running linux based containers on a windows host, the actual volumes will be stored within the linux VM and will not be available on the host's fs, otherwise windows running on windows =&gt; C:\ProgramData\Docker\volumes\
Also <code>docker inspect &lt;container_id&gt;</code> will list the container configuration, under Mounts section see more details about the persistence layer.
Update:
Not applicable for Docker running on <a href="https://docs.docker.com/docker-for-windows/wsl/" rel="noreferrer">WSL</a>.

blocks|key|29116|text|如果您启用了wsl2，您可以在\\wsl$\docker-desktop\mnt\host\wsl\docker-desktop-data\data\docker下的文件资源管理器中找到它|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|29117|entityMap^0|F|1U|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you have wsl2 enabled, u can find it in file explorer under <code>\\wsl$\docker-desktop\mnt\host\wsl\docker-desktop-data\data\docker</code>

blocks|key|2697563|text|我发现我的Docker与WSL+2+(Ubuntu+20.04)的设置使用Windows+10的这个位置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2697564|C:\Users\Username\AppData\Local\Docker\wsl\data\ext4.vhdx|code-block|syntax|javascript|2697565|其中Username是您的用户名。|offset|length|style|CODE|2697566|entityMap^0|0|0|2|8|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I have found that my setup of Docker with WSL 2 (Ubuntu 20.04) uses this location at Windows 10:
<pre><code>C:\Users\Username\AppData\Local\Docker\wsl\data\ext4.vhdx
</code></pre>
Where <code>Username</code> is your username.

blocks|key|29123|text|我使用的是Windows+%2B+WSL+2+(Ubuntu+18.04)，Docker+v19.03。我在以下位置找到了我的Docker卷，在Windows文件资源管理器中键入：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29124|\\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\|code-block|syntax|javascript|29125|每个卷将有一个目录。|29126|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I'm on Windows + WSL 2 (Ubuntu 18.04), Docker v19.03.
I found my Docker volumes in this location, type in the Windows file explorer :
<pre><code>\\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\
</code></pre>
You will have one directory per volume.

blocks|key|2697595|text|如果你在windows上使用Docker+For+Windows，那么Docker是通过VM+(MobyLinuxVM)工作的。您的卷(与其他卷一样)在此虚拟机中！关键是如何找到它们：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2697596|#+get+a+privileged+container+with+access+to+Docker+daemon
docker+run+--privileged+-it+--rm+-v+/var/run/docker.sock:/var/run/docker.sock+-v+/usr/bin/docker:/usr/bin/docker+alpine+sh

#+in+second+power-shell+run+a+container+with+full+root+access+to+MobyLinuxVM
docker+run+--net=host+--ipc=host+--uts=host+--pid=host+-it+--security-opt=seccomp=unconfined+--privileged+--rm+-v+/:/host+alpine+/bin/sh

#+switch+to+host+FS
chroot+/host

#+and+then+go+to+the+volume+you+asked+for
cd+/var/lib/docker/volumes/YOUR_VOLUME_NAME/_data|code-block|syntax|javascript|2697597|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you're on windows and use Docker For Windows then Docker works via VM (MobyLinuxVM). Your volumes (as everting else) are in this VM! It is how to find them:
<pre><code># get a privileged container with access to Docker daemon
docker run --privileged -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker alpine sh

# in second power-shell run a container with full root access to MobyLinuxVM
docker run --net=host --ipc=host --uts=host --pid=host -it --security-opt=seccomp=unconfined --privileged --rm -v /:/host alpine /bin/sh

# switch to host FS
chroot /host

# and then go to the volume you asked for
cd /var/lib/docker/volumes/YOUR_VOLUME_NAME/_data
</code></pre>

blocks|key|29132|text|如果您在放置一个指向docker+"vm“的卷时正在搜索数据的实际位置，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29133|version:+'3.0'
services:
++mysql-server:
++++image:+mysql:latest
++++container_name:+mysql-server
++++restart:+always
++++ports:
++++++-+3306:3306
++++volumes:
++++++-+/opt/docker/mysql/data:/var/lib/mysql|code-block|syntax|javascript|29134|"/opt/docker/mysql/data"或仅/位于\\wsl$\docker-desktop\mnt\version-pack\containers\services\docker\rootfs中|offset|length|style|CODE|29135|希望它能有所帮助:)|29136|entityMap^0|0|0|0|O|Q|1|T|20|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

If you're searching where the data is actually located when you put a volume that is pointing to the docker &quot;vm&quot; like here:
<pre><code>version: '3.0'
services:
 mysql-server:
 image: mysql:latest
 container_name: mysql-server
 restart: always
 ports:
 - 3306:3306
 volumes:
 - /opt/docker/mysql/data:/var/lib/mysql
</code></pre>
The <code>&quot;/opt/docker/mysql/data&quot;</code> or just the <code>/</code> is located in <code>\\wsl$\docker-desktop\mnt\version-pack\containers\services\docker\rootfs</code>
Hope it's helping :)

blocks|key|2487155|text|对于Windows+10+%2B+WSL+2++(Ubuntu+20.04),+Docker+version+20.10.2,+build+2291f61|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2487156|Docker工件可以在|2487157|DOCKER_ARTIFACTS+==+\\wsl$\docker-desktop-data\version-pack-data\community\docker|2487158|数据卷可在以下位置找到|2487159|​|2487160|📷|atomic|2487161|2487162|DOCKER_ARTIFACTS\volumes\[VOLUME_ID]\_data|2487163|2487164|2487165|2487166|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/77e38c1e2734f51b70f392aa4dc025fc.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/5694487abd9ddb545eeb8731cd028e8e.png^0|2|21|0|0|0|29|0|0|0|0|1|0|0|0|0|16|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1G|8|@]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|Q|3|M|5|6|7|1K|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|T|3|M|5|6|7|1O|8|@]|D|@]|E|$]]|$1|U|3|O|5|P|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|V|3|M|5|6|7|1T|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13|14|-4]]|15|$5|Z|10|11|E|$12|16|14|-4]]]]

For <code>Windows 10 + WSL 2 (Ubuntu 20.04), Docker version 20.10.2, build 2291f61</code>
Docker artifacts can be found in
<code>DOCKER_ARTIFACTS == \\wsl$\docker-desktop-data\version-pack-data\community\docker</code>
Data volumes can be found in
<a href="https://i.stack.imgur.com/8yVgv.png" rel="noreferrer"><img src="https://i.stack.imgur.com/8yVgv.png" alt="enter image description here" /></a>
<code>DOCKER_ARTIFACTS\volumes\[VOLUME_ID]\_data</code>
<a href="https://i.stack.imgur.com/y0uGl.png" rel="noreferrer"><img src="https://i.stack.imgur.com/y0uGl.png" alt="enter image description here" /></a>

blocks|key|2487173|text|您可以在Docker+Desktop(Windows)的以下路径中找到与主机关联的卷|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2487174|\\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes|code-block|syntax|javascript|2487175|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

you can find the volume associated with host on below path for Docker Desktop(Windows)
<pre><code>\\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes
</code></pre>

blocks|key|2697726|text|\\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2697727|对我来说也是如此(Windows10家庭版)，很棒。|unstyled|2697728|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>\\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\
</code></pre>
Worked for me as well (Windows 10 Home), great stuff.

blocks|key|2487316|text|在我的例子中，我在wsl2和Windows10上安装了docker-desktop。我在以下位置找到我的图像文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2487317|\\wsl$\docker-desktop-data\version-pack-data\community\docker\overlay2
\\wsl$\docker-desktop-data\version-pack-data\community\docker|code-block|syntax|javascript|2487318|容器、图像、卷、信息都在那里。|2487319|所有图像文件都存储在那里，并被分到几个具有长字符串名称的文件夹中。当我查看每个文件夹时，我可以在"diff“文件夹中找到所有真实的图像文件。|2487320|虽然终端显示路径为"var/lib/docker"，但该文件夹并不存在，实际的文件也不存储在其中。我认为没有错误，"var/lib/docker“只是链接或映射到真正的文件夹，就像这样|2487321|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case, i install docker-desktop on wsl2, windows 10 home. i find my image files in
<pre><code>\\wsl$\docker-desktop-data\version-pack-data\community\docker\overlay2
\\wsl$\docker-desktop-data\version-pack-data\community\docker
</code></pre>
Containers, images volumes infos are all there.
All image files are stored there, and have been seperated into several folders with long string names. When i look into every folder, i can find all the real image files in &quot;diff&quot; folders.
Although the terminal show the path &quot;var/lib/docker&quot;, but the folder doesn't exsit and the actual files are not stored there. i think there is no error, the &quot;var/lib/docker&quot; is just linked or mapped to the real folder, kind like that

I'm trying to learn docker at the moment and I'm getting confused about where data volumes actually exist.

I'm using Docker Desktop for Windows. (Windows 10)

In the docs they say that running docker inspect on the object will give you the source:<a href="https://docs.docker.com/engine/tutorials/dockervolumes/#locating-a-volume" rel="noreferrer">https://docs.docker.com/engine/tutorials/dockervolumes/#locating-a-volume</a>

<pre><code>$ docker inspect web

"Mounts": [
 {
 "Name": "fac362...80535",
 "Source": "/var/lib/docker/volumes/fac362...80535/_data",
 "Destination": "/webapp",
 "Driver": "local",
 "Mode": "",
 "RW": true,
 "Propagation": ""
 }
]
</code></pre>

however I don't see this, I get the following:

<pre><code>$ docker inspect blog_postgres-data
[
 {
 "Driver": "local",
 "Labels": null,
 "Mountpoint": "/var/lib/docker/volumes/blog_postgres-data/_data",
 "Name": "blog_postgres-data",
 "Options": {},
 "Scope": "local"
 }
]
</code></pre>

Can anyone help me? I just want to know where my data volume actually exists is it on my host machine? If so how can i get the path to it?

Locating data volumes in Docker Desktop (Windows)

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我现在正在尝试学习docker，但我对数据卷实际存在的位置感到困惑。我正在使用版的Docker桌面。(Windows 10)在文档中，他们说在对象上运行docker inspect会给你提供源代码：$ docker inspect web"Mounts": [    {        "Name": "fac362.....

问在Docker Desktop (Windows)中查找数据卷
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Docker Desktop (Windows)中查找数据卷EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Docker Desktop (Windows)中查找数据卷
EN