I was following the tutorial using "Docker Desktop for Windows" and received the following exception on execution of the "docker run..." command:
docker run -dp 3000:3000 -w /app -v "$(pwd):/app" node:12-alpine sh -c "yarn install && yarn run dev"
docker: Error response from daemon: status code not OK but 500: ���� FDocker.Core, Version=3.0.0.50646, Culture=neutral, PublicKeyToken=null ocker.Core.DockerException WatsonBuckets System.Collections.IDictionarySystem.Excepti ocker.Core.DockerException Filesharing has been cancelled
Adding the base-path as a shared resource to the docker configuration solved the problem.
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.
