Docker Keeps Deploying Fresh Instance On Target or Project Change

Hi.
I have a project with NodeJS/Docker local target. I had recently upgraded to 4.0.1.
Before the upgrade & even with 4.0.1 Docker worked as expected - start Wappler and it starts Docker and project is ready to be used.
But suddenly since past week, something has broken and now everytime I start Wappler, it starts Docker and does a deployment. The npm install step takes a huge amount of time as well.
I did play around with the targets as there were some additions and deletions, but I have no idea what went wrong and why does my local Docker deployment is causing this issue.

Here is my dockerfile:

FROM wapplerio/node-14
COPY ./ /opt/node_app/

ENV NODE_ENV development
WORKDIR /opt/node_app
COPY package.json .
RUN npm install --no-optional
CMD [ "nodemon", "--legacy-watch", "./index.js" ]

If someone can please help me make sense of what is wrong in this file here, it would be great.

@patrick ??

Found the issue. It was this line.

Maybe between managing dockerfiles of local, staging & production targets, I copied this from production docker file to local.

1 Like

Yes this is only needed for remote targets to copy all your web site files.

For local targets there is a direct mapping to your local folder, so no need to copy.

1 Like