Allow us to define which packages need to be removed before installing
the desired ones.
Fixes use of role on systems where it was desired to install upstream
docker but the system one was already installed.
Change-Id: Ib6ae0a8fba937901b29565e2d36486eccf4f67bb
At the moment, the build registry is not used inside Kubernetes jobs
and it is required to override the entire pre.yaml just to enable it.
This patch adds an option of using docker_use_buildset_registry inside
install-docker which can be used in order to install Docker and letting
it use the buildset registry simply by adjusting the job.vars
Change-Id: I1b42eac6accbf7c350aee76d18a823ba6327548d
The install-docker role currently takes care of setting up Docker
however it lacks the ability to install docker-compose at the moment
which is quite useful.
This adds a variable which defaults to false that allows you to use the
role to install docker-compose. It was decided to be put within the
install-docker role because that role already manages the repository
configuration and therefore provide consistency with the repository that
is used to install docker-compose.
Change-Id: Ia6f4ed88b4baf53bd671c7a7b48a1564ff2c866d
The docker mirror URL can now be set using the following options,
`docker_download_fqdn` and `docker_mirror_base_url`. These
variables will allow folks to use this role with custom mirrors.
To accomodate this change, the repo files have been moved into
templates and now use the jinja2 extension.
Not all supported distros have the ability to install docker
using the upstream mirrors. To ensure a high degree of success
a new sanity check has been added to validate the mirror url
content when upstream installation has been enabled.
Change-Id: Ib9d50581d0df89e36d47dd523efd1adc95fdf4ac
Signed-off-by: Kevin Carter <kecarter@redhat.com>
This change adds the ability for the zuul provided role for docker
installation to support multiple distros automatically. With this
change the role will dynamically load variables based on the
target operating system.
While the default to install from upstream reamains unchanged, the
role will now fall back to installing using the distro packages
in the event there's is a fault with the upstream tasks or if an
upstream task file has not been implemented.
> stubbs for upstream implementation task files have been created.
With this change the role will now support, debian (and family),
opensuse, and red hat (and family). The upstream installation process
is using the documented steps from upstream docker, as found here
[0].
The default "ubuntu_gpg_key" as renamed to "docker_gpg_key" as its
now used for more than one distro.
The daemon.json.j2 template has been removed. This template was
stored here but unused by this role.
[0] https://docs.docker.com/install/linux/docker-ce/fedora/
Change-Id: Ie52444f8c62d6e2f86ce9ba1c17795dd9a6471d2
Signed-off-by: Kevin Carter <kecarter@redhat.com>
Allow custom docker_group which is needed on CentOS when
use_upstream_docker: false as is value is 'dockeroot'.
Assures that docker service is started, which is not always true
with all distributions.
Validates that we can talk with docker at the end.
Change-Id: I993c4ac35055a2a18b5b0fb32c8b230e04b7eb87
There are two different ways to install docker - from upstream repos or
from distro. At the moment each of these carries with it the need for a
different caching proxy setup.
Add a role that will install docker from upstream by default, but which
also supports installing directly from distros. The role also sets up
the registry proxy appropriately for each.
This role at the moment only works on ubuntu. It should obviously be
updated to work on centos and fedora as well.
Needed-By: https://review.openstack.org/580160
Change-Id: I7d6bac68a2c0fecf13a8bd9535a3fdeb85e7d999
vass