---
title: "Comment by Krys Alead on \"Dockerize your Development Environment for NodeJS\" | Hashnode"
description: "Hi, Thanks for the article. I would nevertheless not use &quot;latest&quot; as a tag as depending on when you build your image you got a different version of no"
url: "https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae/comment/5f7efa0db4179e7e858817c1"
---

[Discussion](https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae)

Comment [Dockerize your Development Environment for NodeJS](https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae)

[Krys Alead](https://hashnode.com/@Krysalead)

[Oct 8, 2020](https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae/comment/5f7efa0db4179e7e858817c1)

Hi,

Thanks for the article. I would nevertheless not use "latest" as a tag as depending on when you build your image you got a different version of node. Something I missed is when do you start your server (not the docker image) what is the magic happening that make your docker-compose up command running the npm start command?

[Jakob Klamser](https://hashnode.com/@KlamserDEV)

[Oct 8, 2020](https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae/comment/5f7efa0db4179e7e858817c1#reply-5f7f0409b4179e7e8588186f)

You are totally right about "latest". If you are just in development I don't mind it. But right before you deploy the first version of your software you need to specify a version.

For the npm start, I had an old Dockerfile. I updated it

[Krys Alead](https://hashnode.com/@Krysalead)

[Oct 8, 2020](https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae/comment/5f7efa0db4179e7e858817c1#reply-5f7f0c80b4179e7e858818fd)

Hi [Jakob Klamser](https://hashnode.com/@KlamserDEV)

I thought your article was about developing with Docker and Node and sharing the image with other developers requires to fix the version. And indeed once you are happy with your dev you need to fix it :). I was reasoning as a development environment for a large team.

[Jakob Klamser](https://hashnode.com/@KlamserDEV)

[Oct 8, 2020](https://hashnode.com/posts/dockerize-your-development-environment-for-nodejs/5f7b7a6b9d088e603ef395ae/comment/5f7efa0db4179e7e858817c1#reply-5f7f0d83cbb01b7e6418592d)

Hi [Krys Alead](https://hashnode.com/@Krysalead)

you are free to do so whenever you please. If you are sharing your development environment with your whole team fixing the nodejs version should be prioritized.

Totally agree with you there :)
