Versions Compared

Old Version 1

changes.mady.by.user Jim Jokl (virginia.edu)

Saved on

compared with

New Version 2

changes.mady.by.user Jim Jokl (virginia.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Statement

All Docker containers created or maintained by TIER are built to the specifications described in this document.  We have tried to limit the requirements to the 

Background

In order to facilitate support, TIER has made decisions throughout the course of the project to standardize on certain sub-components and and more recently to ensure that TIER containers are compatible with our default orchestration strategy of using Docker Swarm mode via Compose.  

Specification

  1. Base Linux Image
    1. Centos 7
      1. Standard maintained Centos 7 image
      2. (Under Discussion) potential use of

  2. Compatibility/ease of use with SWARM while not breaking other options.

  3. Base Image - Centos 7 - one of:

  4. Standard Centos 7 image we have been using with the addition of supervisord when needed

      1. Centos 7 image from Dockerhub that includes what is needed to use systemd as init (instead of supervisord)
      1. .  We may enable this option is optaining/implementing the logging changes we need to supervisord are hard - - https://hub.docker.com/r/centos/systemd/
  7. Servlet Engine
    1. Tomcat will be used whenever a servlet engine is needed.
  8. Java Distribution
    1. Oracle's Java distribution will be used whenever Java is needed.
  9. Database
    1. If a relational database is provided, MARIADB will be used.
  10. Multi-Process Container
    1. Supervisord will be used whenever a container needs more than one process.
  11. Container Configuration
    1. Standard Data
      1. Containers may receive configuration data via the environment as described below for Secret Data (6.b)
      2. Configuration data may be mounted into the container from external storage
      3. Configuration data may be "burned" into the container while it is being built.
      4. There are many trade-offs between ii and iii, some environments will choose to enable the end user to build their containers using either method.
    2. Secret Data
      1. The preferred mechanism to support data that must be protected (e.g., passwords, keys, etc.) is Swam-mode Docker Secrets
  12. Compatibility/ease of use with Docker SWARM mode, using Docker Stack Deploy and Compose files, while working to not preclude other orchestration options.

  1. Secret Processing

    1. Assume secrets are mounted in /run/secrets (to support compose in swarm)

    2. Secret Availability - in-container startup script behavior

      1. Accept the secret in the environment, e.g.,

...