| Age | Commit message (Collapse) | Author | Files | Lines |
|
Updated build.py to reflect this change.
Deprecate --template option and make it a noop.
Change-Id: I7cd98d1ee684a4c64984a49597159868152683b2
Partially-Implements: blueprint remove-docker-dir
|
|
|
|
Sam thinks this is the cause of the permissions issue. Whether it
is or not, it is not necessary in the base image. Sam suggested
using the same libraries throughout the deployment related to
mysql - seems to make sense to me.
Change-Id: I14ed99db7ceccd6d6231f29bd24e1dcd0246bf92
Closes-Bug: #1486374
|
|
This patch allows to add instructions to final images
like setting runtime environment variables or deleting
build time HTTP proxies
Change-Id: I23ad325e0898d77804a22038ddc618e1e49afd88
Partially-Implements: blueprint add-proxy-to-dockerfiles
|
|
In MariaDB we adjust the dependecies of what we install there as well
adding only what is appropriate for the install.
In Ansible we adjust some templates to all work around differences
between the different Linux families.
Change-Id: Ibc26e2f4d4a732630632d3ed27fb595b6fe019d2
Partially-Implements: blueprint install-from-ubuntu
|
|
The previous method of using the API image for a data container
worked, but resulted in more data being bindmounted and copied
into the system. This patch resolves that by essentially using
a distro-type as a FROM in a Dockerfile to generate
distro-type-data. Further all of the data containers used
throughout ansible are modified to use this new data container.
Change-Id: I8846573d4f2d4b98d4f46c770bfefc6d4c5cd0b5
Partially-Implements: blueprint one-data-container
|
|
While the existing FROM line is technically correct, prefer we
use jinja tmeplating for the whole thing, so that we can remove
the special casing of the build.py script once the docker dir
goes.
Change-Id: I27efcd55f1b45d32e4504734edf9e1a305696ac1
Partially-Implements: blueprint dockerfile-templates
|
|
Change-Id: I4a1e97f683323176aa8e77ac18be16576941dbdb
Partially-Implements: blueprint dockerfile-template
|