Recently, I encountered an issue with my React.js app after dockerizing it. Everything was running smoothly until I updated the node version to 17 and began experiencing errors. To resolve this, I reverted back to using node version 16 in my docker image. However, ever since making this change, I have been unable to run the docker image on the specified port.
Below is the content of my dockerfile:
ROM node:16.10-alpine as build
RUN mkdir /app
WORKDIR /app
COPY /front-end/dashboard/package.json /app
RUN npm install
COPY ./front-end/dashboard /app
RUN npm run build
# Install `serve` to run the application.
RUN npm install -g serve
# Set the command to start the node server.
CMD serve -s -n build
# Inform Docker about the port we'll be utilizing.
EXPOSE 5000
Despite setting up a build and attempting to serve it on port 5000, I am now encountering difficulties which were not present before.
The output displayed in docker indicates:
Serving! │
│ │
│ - Local: http://localhost:3000 │
│ - On Your Network:
Upon accessing localhost:3000, there are no signs of activity even though the intended functioning port should be 5000. Unfortunately, I am unable to run the docker image's build on port 5000 as previously achieved. Any insights into why the build now fails to run on port 5000?
My attempt at resolving the issue by executing 'docker run -p 5000:5000' has proven unsuccessful.