Container image

135

A container image is a ready-to-run software package, containing everything needed to run an application: the code and any runtime it requires, application and system libraries, and default values for any essential settings.

Stuff you wanna know:

  1. If you have a containerized application and want to make changes, you need to build a new image that includes the change, then recreate the container to start from the updated image.
  2. Container images are executable software bundles that can run standalone.
  3. A container image represents binary data that encapsulates an application and all its software dependencies.
  4. You typically create a container image of your application and push it to a registry before referring to it in a Pod.
  5. If you don’t specify a registry hostname, Kubernetes assumes that you mean the Docker public registry.
  6. Container images are usually given a name such as pause, example/mycontainer, or kube-apiserver.
  7. Images can also include a registry hostname; for example: fictional.registry.example/imagename, and possibly a port number as well; for example: fictional.registry.example:10443/imagename.

More stuff: