Docker neatly packs your application and its environment so it runs without errors in production just like it does on your local machine. Like The Flintstones worse.ĭocker is one such technology that makes application deployment less frustrating for developers.

Luckily, deploying applications has become easier in recent years and there's a constant flow of new technologies.

When you're learning to code, learning to host on top of that can be insane. Deploying applications is not trivial and some people are paid to do it full time. Is there an issue with my code or is every build like that? Why does it have to be this hard to get my application in front of my users? When you finally manage to fix the issue a new one pops up. Your application crashes when you start it. noninteractive to remove this prompt.You've finished developing your website and now you want to put it online except you're running into a ton of problems. ? This runs the production build, are you sure you want to run it? Add (Y/n)Īnd I got the following error after execution docker-compose build. ? This runs the production build, are you sure you want to run it? Add -noninteractive to remove this prompt. When I start the production build manually, I have to type 'Y' to start it finally: > razzle build My issue is that I wish to have everything automated, without providing responses on the command line manually after docker-compose up.

(in package.json for scripts->build is set 'razzle build'. In my Dockerfile for ' node' I want to finally build the production build and start the node server.īy using RUN npm run-script build, the razzle production build should be started to run. So, I am using containers / services for ' node', ' traefik' and ' db' (postgres db) within my docker-compose YAML file. I dockerize a web application using docker-compose.

Nodejs dockerfile