Skip to content

Commit 7ca3aae

Browse files
Update 05_persisting_data.md
Added info for those running containers in Windows and are curious to find where is /var or what it would be like if they were running Windows containers
1 parent 753cf3e commit 7ca3aae

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

content/get-started/workshop/05_persisting_data.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -194,6 +194,36 @@ You should see output like the following:
194194
The `Mountpoint` is the actual location of the data on the disk. Note that on most machines, you will
195195
need to have root access to access this directory from the host.
196196

197+
This path is relative to Linux host machine and also in case you are running containers on Windows OS,
198+
it means you are using Linux containers. Although, Windows containers have limited image support comapred
199+
to Linux containers (such as contiki-ng), you can try to switch from Linux Container to Windows containers
200+
and run following command to witness the relative path of volume changes on Linux based based to Windows based path.
201+
202+
```console
203+
docker volume create todo-app
204+
docker volume ls
205+
```
206+
207+
you will see volume by name todo-app, now perform volume inspection to see it's path
208+
209+
```console
210+
docker volume inspect todo-app
211+
```
212+
your output will look like
213+
```
214+
[
215+
{
216+
"CreatedAt": "2024-12-16T11:24:56+01:00",
217+
"Driver": "local",
218+
"Labels": null,
219+
"Mountpoint": "C:\\ProgramData\\Docker\\volumes\\abc\\_data",
220+
"Name": "abc",
221+
"Options": null,
222+
"Scope": "local"
223+
}
224+
]
225+
```
226+
197227
## Summary
198228

199229
In this section, you learned how to persist container data.

0 commit comments

Comments
 (0)