My Take on an Azure Open Source Cross-Platform DevOps Toolkit–Part 7

Stopping the previously running container (myapp)

As we enter step 5 we will now begin to think about testing the running container.

But before we can do that we have to make sure that firstly stop all running containers. Once we're sure that all containers are stopped, we can run the container we just built. So this post is about stopping the container.

So between steps 3 and 4 we will stop the old running container and run the new one.

Figure 1: The big picture

Jenkins Pipeline Definition

The next 2 sections of our pipeline that need to be built.

Figure 2: The current work for our pipeline

Explanation for StopRunningContainersLocally.py

Source code for StopRunningContainersLocally.py

Figure 3: Source code for StopRunningContainersLocally.py

Validating correct operation of StopRunningContainersLocally.py

The docker ps command reveals that myapp is running. Then, python3 StopRunningContainersLocally.py successfully stop myapp from running. Finally, we run ShowPipelineState.py to validate that the state is correctly being recorded.

Figure 4: Testing StopRunningContainersLocally.py

Let's run a docker ps to make sure that the container is not running (myapp).

Figure 5: Proof that the container is not running

Conclusion

We finished the work for stopping our running container. This important because our pipeline needs to do these steps:

1. Build a new container
2. Stop the old container that is running
3. Run the new container

In the next post we will illustrate how to start the container that is freshly built.