foreword
When using Docker to deploy and start containers, we often encounter a problem, that is, the docker run command is not recorded, so that the previous start command cannot be accurately found during subsequent redeployment. This situation bothers us. In order to solve this problem, I will share a method that allows you to easily find the startup command at that time, which is convenient for subsequent redeployment work. Let's take a look at how to record and retrieve your Docker container's start commands so you can quickly find and reuse them when needed.
Install the Runlike tool
runlike is a tool for viewing the startup commands of Docker containers. It allows you to view the container's startup command in a more intuitive way, including the container's name, image, mounted volume, and other parameters.
Runlike is a tool written in Python, in order to use Runlike, you need to install the pip package manager first.
yum install -y python38
install runlike
pip3 install runlike
View container startup commands
runlike -p <container_id_or_name>
where <container_id_or_name> is the ID or name of the container you want to view. After running the command, the container's start command and its arguments are displayed.
Practical case
View the previously deployed xxl-job-admincontainer
runlike -p xxl-job-admin
You can see that there is also a thoughtful line break, which is really a good skill, and you don't have to worry about forgetting the container startup command anymore.
epilogue
By installing and using the runlike tool, we can easily view the startup command of the Docker container, which solves the problem of redeployment difficulties caused by unrecorded startup commands. This is very helpful for container management and redeployment, improving the efficiency of development and deployment.
In everyday Docker usage, we recommend getting into the habit of recording container startup commands so that you can quickly find the command you need when you need to redeploy or share configuration. At the same time, it is also a good practice to regularly back up important container configuration information.
I hope this article helps you and makes it easier for you to manage and deploy Docker containers.