Unable to get started
See original GitHub issueWhat you did:
Followed the docs. Well, both versions of the docs, since the site and the readme have different ‘Getting started’ steps.
What happened:
Following the docs
sh: build-and-start.sh: No such file or directory
Following the Github readme
Step 5/9 : COPY package-lock.json . ERROR: Service 'mockit-server' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder079289765/package-lock.json: no such file or directory
Problem description:
I would love to give this a chance, but am unable. Not sure if this is me missing an ‘obvious’ but undocumented step, or if it’s something that’s missing in the repo.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Can't start a task even though it's really important?
Are you having trouble starting a task even though it's really important? You aren't alone. This is a very common issue for adults...
Read more >Can't Get Started? Can't Catch Up? - Psychology Today
Six ways to get going on that project you've been avoiding. · 1. Set your goal. · 2. Review your goal, and then...
Read more >Do You Know The 2 Reasons You Have Trouble Starting Tasks?
One of the reasons for your inconsistency in starting your important work is that there is insufficient dopamine released in the executive ...
Read more >Why Getting Started Is So Difficult for Adults with ADHD
Getting started on tasks is difficult for adults with ADHD and executive dysfunction. Learn how and why task initiation is impaired.
Read more >What's Stopping You from Getting Started (and What to Do ...
Lack of financial security: · Lack of confidence in your plan: · Lack of confidence in yourself: · Too much on your plate...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After opening my eyes and reading the error message, I figured out I already had something running on that port. Stopping my service on that port and re-running the command made it all work!
EDIT: However, the missing
package-lock.json
is still an issue. I’d shoot in a PR, but not sure if that would give the correct versions that you’re intending to use 😃Thanks for the details and info @JDansercoer