Section, "Diving into our Volume" subsection, "Accessing Volume data directly on Docker Desktop"
Save other Docker Desktop for Windows users the same hassle I had of verifying the non-existent volume repository: "Mountpoint": "/var/lib/docker/volumes/todo-db/_data",
In WSL2, Docker Desktop for Windows, the repository is located at: \\wsl$\docker-desktop\mnt\host\wsl\docker-desktop-data\data\docker\volumes\todo-db\_data
Ref: https://stackoverflow.com/a/63668192/14096774
The original language implies that SQLite is not an "actual" database engine, which is of course not the case! SQLite is a very capable and ubiquitous database engine. It's not appropriate for many applications, though, so perhaps the document here can simply read "different" rather than "actual". I recognize this is a bit particular, but hey-- that's how I perceived the language on my first read, and I don't even particularly like (or use) SQLite anyways! I do respect the technology, though, and thought it'd be kind to change the language so as to remove all possibility of misinterpretation.
The Dockerfile listed above specifically uses package.json, but the
output listed for the build lists package*, which is inconsistent. The
React example later in the doc uses package*, which would be consistent
with the output, but this should fix the mismatch for the beginner going
through the tutorial for the first time.
Additionally, the sentence "Build the Docker image now using 'docker
build' again" might be confusing to a beginner. I specifically tested
running this exact command and it gives an error message. Specifically
using the exact command needed to build this target shouldn't take up
too much space.
Signed-off-by: mikesir87 <mikesir87@gmail.com>
Imported from dockersamples/101-tutorial, removed other languages
for now, and replaced PWD references with Docker Desktop.
