Skip to content
Snippets Groups Projects
  1. Mar 26, 2015
  2. Mar 25, 2015
  3. Mar 24, 2015
  4. Mar 23, 2015
  5. Mar 22, 2015
    • Steven Dake's avatar
      Make mariadb use a data container without a bindmount · c2b92c5e
      Steven Dake authored
      
      A data container is meant to operate without bindmounts.
      
      Change-Id: I2624a63fd75db7ed8050054c17e19885f8a7ac8a
      Co-Authored-By: default avatarDaneyon Hansen <(danehans@cisco.com)>
      c2b92c5e
    • Steven Dake's avatar
      Make nova-compute-network use a data volume container · f4fd47dc
      Steven Dake authored
      A data volume container is far superior to bind mounting the
      host's shared directories.  It preserves the idempotency,
      immutability and declarative properties of the containers.
      
      The way this works in practice is that a data volume container is
      created.  Then when the containers start they use LVM to access
      the filesystem where /var/lib/docker is contained.  Then the
      container startup logic bindmounts the data volume stored on the
      host filesystem in /var/lib/docker/vfs/dir/ID.  This prevents
      people with access to the host operating system from damaging
      the contents of the data container.
      
      It does mean that now we must use tools/stop to stop our containers
      rather than tools/cleanup-containers -f.
      
      This is a containers best practice.  For more details see:
      
      https://docs.docker.com/userguide/dockervolumes/
      
      Big credit goes to Danyeon Hansen for seeding this idea in the
      mariadb containers.
      
      Note occasionally docker-compose start/stop seems to not want to stop
      a container.  This bug needs to be addressed upstream separately
      from our utilization of this best practice.
      
      Change-Id: Iaa1419f606e1b1b7a7560a095c49e79d643164f1
      f4fd47dc
  6. Mar 21, 2015
  7. Mar 20, 2015
Loading