Author: Tianle Yuan

Run container by using docker run

Safely running Docker Container

Instead of running docker run --rm dev in the terminal, I suggest directly using Docker Desktop to run docker image that you cloned from the Docker Hub or the one created by yourself ( see in A good model for Docker Image initialization or in Confluence )

If you close your terminal window that ran docker run --rm dev, it will somewhat pause your container then you can not re-start the docker container you created again because you have already closed your terminal process. (This case also equals to you pause your container in Docker Desktop, and you suddenly turn Docker Desktop off. If you reopen the Docker engine again and try to start the container, you are forbidden to do it. I struggled with this lots of times at the start.)

Instead, I directly run the image I have in Docker Desktop. And once I want to stop my container (save all the installed files in it and run again in the future) and shut down my laptop, I directly click stop of the container and turn off the Docker Desktop engine for next time use.

Danger

(It doesn't mean you cannot run the terminal anymore. After you run the container through the Docker Desktop engine, you can open any terminal to edit your container status. Just at this time. closing the terminal will not affect your container process.)

Comments