re: Explain Like I'm Five: Can junior developer make use of docker in any way VIEW POST


Containers are what you make of them. At the very least, they can be useful for doing code-testing (regardless of where that code is going to run). Basically:

  1. Spin up a testing-harness container
  2. Make your code visible/testable to the container
  3. Invoke testing-harness against the container

E.g., if I have code where I would normally just say/pray "this works on <DISTRO_A> and should be portable to <DISTRO_B>", I can spin up a <DISTRO_B>-flavored container and run it in that context without having to stand up a whole VM to do so.

Code of Conduct Report abuse