Issue with Docker, can't get started
See original GitHub issueHey!
I followed up the Docker Development guide:
git clone https://github.com/IcaliaLabs/alpha.gitcd alpha- But I get this error when composing up the container:
docker-compose up web
Starting alpha_web_1 ... done
Attaching to alpha_web_1
yarn start v0.21.3
$ cross-env NODE_ENV=development node server
web_1 | sh: 1: cross-env: not found
error Command failed with exit code 127.
alpha_web_1 exited with code 1
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Docker tutorial 'Getting Started' doesn't work - Stack Overflow
As the tutorial says, first go to the app directory, create a Dockerfile there and then build and run. This should work. 3000:80...
Read more >Troubleshoot Docker Engine installation
Unable to connect to the Docker daemon This error may indicate: The Docker daemon isn't running on your system. Start the daemon and...
Read more >unclear instructions, hard to start, where to create Dockerfile ...
I am new to docker and I try to follow your "Getting started" example and it is not clear what to do: Building...
Read more >How to Resolve the “cannot connect to the Docker daemon ...
How to Resolve the “cannot connect to the Docker daemon” Error · Method 1: Check the Docker Engine · Method 2: Assign Ownership...
Read more >What to Do if Docker Desktop for Windows Does Not Start
Remove Docker in “Add or remove programs”; Restart your computer; Install Docker as Administrator (and not by running the installer directly).
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 Free
Top 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

@CharlieIGG it works, ty! But I don’t understand why. The dev.Dockerfile also includes the command
RUN yarn installHow can this “issue” be corrected? I want to start my container using
docker-compose up -dand avoid jumping inside the container to install yarn every time.Thanks @kurenn !
Closing