If the user runs that command "from the source code folder", i.e.
`getting-started`, docker will bind-mount getting-started to the
container's `/app`, which leads to error
`error Couldn't find a package.json file in "/app"`. It needs to bind
`getting-started/app` instead.
So, be explicit to the reader to be on the app source's directory
`getting-started/app` before running the command.
The command for bind mount doesn't run in Ubuntu if the user is not in the source code folder. At least, for me didn't work. So I specified that to prevent errors and bugs.
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.
Signed-off-by: mikesir87 <mikesir87@gmail.com>
Imported from dockersamples/101-tutorial, removed other languages
for now, and replaced PWD references with Docker Desktop.
workaholic-gh
Michael Irwin
Stefan Scherer
yuu
Oliver Howell
Tim McEwan
zipperer
Telescu Nicolae
spicylentils
Eric Hays