If I would like to use it as a development environment for Node.js, is it alright to just docker run -d?
Do I really need the below?
--interactive , -i Keep STDIN open even if not attached
--tty , -t Allocate a pseudo-TTY
Asked
Active
Viewed 1,472 times
0
geoyws
- 3,326
- 3
- 35
- 47
-
-d flag is for detaching the process from the shell that you are running. So the process will run in the background – Subbu Jul 22 '19 at 04:48
-
Possible duplicate of [what is docker run -it flag?](https://stackoverflow.com/questions/48368411/what-is-docker-run-it-flag) – David Maze Jul 22 '19 at 10:34
-
@geoywas did you check my answer? – Adiii Jul 23 '19 at 17:34
1 Answers
1
In a normal scenario, there is the only one difference
-dit Run the container in the background
-it Run the container in the foreground and will allocate a pseudo-terminal.
But what if the entry point is bash? like in the case of ubuntu-dockerfile. As they believe that the user will override the CMD as per their need or dependent Dockerfile.
# overwrite this with 'CMD []' in a dependent Dockerfile
CMD ["/bin/bash"]
So in this case, when you only specify -d your container will be stopped as soon as it started. So what you need to allocate pseudo-terminal by adding -dit.
As you can see that the container is not running, let check-in stoped container.
so we can that container is exited a minutes ago. Let try with -dit
We can see that the container is running. Same case with alpine if you run alpine with -d it will also stop.
docker run -d alpine
This will exit as soon as it started, so -dit will Allocate a pseudo-TTY as mentioned in the documentation.
Adiii
- 54,482
- 7
- 145
- 148