The previous posts in this series on Docker have looked at running containers to run services, specifically a web server and database server. However, Docker allows containers to be created, run, stopped and destroyed so cheaply that they can be used to run a single job. This job could be a script or even a single command. Unlike a service, a job will stop running when it’s complete. A container running a short lived job can be set to automatically stop and remove itself once the job is complete. If the job needs to be run again, it is reasonably efficient for Docker to start up a brand new container as required.
Don’t Panic!
Stuart 'Stevie' Leitch's blog on Software Development, Java Technologies, Security and TestingArchives
Tags
apm appdynamics appender archetype blame bug ci container DBUnit deploy docker Dockerfile Docker Hub Enzyme hibernate Jest jetty jsp junit maven mock MockMVC MySQL React ReactJS Rule Security SOAP spanners spring Spring-WS spring boot spring cloud data flow spring mvc spring security tapestry test testing tomcat Twilio unit test VM voicexmlriot windows WithMockUserLicence
Don't Panic! blog and example code by Stuart 'Stevie' Leitch is licensed under a Creative Commons Attribution 3.0 Unported License.