CODEWITHSUNDEEP
reactjsdockercreate-react-app
Jason McFarlane
Jason McFarlane

Reputation: 2175

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

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

Upvotes: 44

Views: 17530

Answers (9)

shmuels
shmuels

Reputation: 1403

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.

Upvotes: 1

Pankaj Bodhe
Pankaj Bodhe

Reputation: 11

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

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

Upvotes: 1

Supabase Enjoyer
Supabase Enjoyer

Reputation: 380

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

Upvotes: 8

Sujeet Kumar Mishra
Sujeet Kumar Mishra

Reputation: 41

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

Upvotes: 4

Abhishek Sinha
Abhishek Sinha

Reputation: 1219

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

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

Upvotes: 4

Smita
Smita

Reputation: 129

Running the command with -it worked for me:

docker run -it -p 3001:3000 Imageid

Upvotes: 12

h01m3s
h01m3s

Reputation: 290

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

Upvotes: 27

Ramy M. Mousa
Ramy M. Mousa

Reputation: 5943

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

Upvotes: 52

Jason McFarlane
Jason McFarlane

Reputation: 2175

So nothing is wrong with the setup turns out there is an open issue for this.

https://github.com/facebook/create-react-app/issues/8688

Downgrading to 3.4 solves for now

Upvotes: 4

Related Questions