Docker container exiting immediately after starting when using npm init react-app

user_8273908 0
Viewed 13281

I am trying to start a Docker container with a react project, the project is created using npm init react-app.

This is my docker file 

# Specify a base image
FROM node:alpine

WORKDIR /usr/app

# Install some depenendencies
COPY ./package.json ./
RUN npm install
COPY ./ ./

# Default command
CMD ["npm", "run", "start"]

Docker build . creates an image successfully (with a lot of npm warnings) and then when I run Docker run <image> this is the output in my terminal

> mytest@0.1.0 start /usr/app
> react-scripts start

ℹ ｢wds｣: Project is running at http://172.17.0.2/
ℹ ｢wds｣: webpack output is served from 
ℹ ｢wds｣: Content not from webpack is served from /usr/app/public
ℹ ｢wds｣: 404s will fallback to /
Starting the development server...

Soon as it hits Starting the development server... it stops running in my terminal. If I check Docker ps I can see no containers are running, if I run Docker ps -a I can see a container was started up and then exited immediately.

Docker logs shows the terminal output above, anybody run into this situation? Its only with my npm init react-app project, my other nodejs + express projects run fine with the exact same docker file

create-react-app docker reactjs
9 Answers

I tried downgrading but it didn't work. What worked for me is in docker-compose file in the react app sector I added:

stdin_open: true

This solution is also suggested here: issue on github

user_34272520

docker run -it -p 80:3000 imagename resolve my problem.

user_48577570

Running the command with -it worked for me:

docker run -it -p 3001:3000 Imageid
user_133642060

I solve the problem. Inside package.json replace "react-scripts": "3.4.1" to "react-scripts": "3.4.0"

Then rebuild image and It works ! They mess up something with react-scripts": "3.4.1" Just use version 3.4.0

user_103207790
user_82739080

Ran into the same issue. -it flag resolved the issue.

docker run -it -p 3001:3001 <image-id>
user_48943680

I got the same issue as you and just ran the above command to fix it:

sudo docker run -it -p 3001:3000 Image-Name

Hope it helps

user_56118300

You can use the below with -itd flag as well.

sudo docker run -itd -p 3001:3000 Image-Name
user_155727370

Using the suggestion mentioned in this ans. on stackoverflow and on github, of adding

ENV CI=true to the Dockerfile before CMD ["npm", "run", "start"], worked.

I'm not sure why this works. It may have something to do with this point. You can read more about the env CI=true in the react docs.

user_95307900
Related