9 Commits

Author SHA1 Message Date
Clark Boylan
17ba858b19 Update our gitea images to bullseye
To do this we also update jinja-init to bullseye and gitea seems to be
the only user of this image. The impact of this should be fairly self
contained to gitea.

Note this update isn't urgent, but good hygiene. We should coordinate
this update with the 1.15.x gitea upgrade and do them in such a sequence
that we can identify problems easily if they pop up.

Change-Id: Ia0075416a1d8a067cfecd26c03f8db9641cbcb89
2021-09-15 10:49:42 -07:00
Clark Boylan
421a71e145 Be explicit about using python3 in docker images
Our docker python-base image is a python3 image where python and python3
point to the same version of python which happens to be a 3.x depending
on the specific base image.

One of the things that came up at the PTG is that we'd like to start
identifying where we use python2 in order to port to python3. That is
made a bit more difficult when we use `python` assuming it is `python3`
as we do in our docker images.

Update the images to use `python3` to make this a lot more explicit and
clear that we don't need to port these items.

Change-Id: I54e8f128f0cb8fbbdf54e3748384470262bef3a9
2020-06-09 09:30:56 -07:00
Monty Taylor
650392c700 Start making 3.8 python images
base and builder are currently pinned to 3.7, which makes it hard
to consider upgrading to python-3.8. To help with that, make
python-3.7 and python-3.8 images, but point latest as 3.7 for the
time being. Then add version-specific provides and FROM lines
so that we can start being deliberate and clear about our version
choice.

Change-Id: Ibf1d846d5c4a005547785124567ce2900e272a7a
2020-03-25 17:45:39 -05:00
Monty Taylor
ccaf54c866 Base gitea-init on opendevorg/python-base
So that we can keep one python base image for our python things,
base jinja-init and gitea-init on python-base. Also, tie jinja-init
to python-base in the dependency graph and gitea-init to jinja-init.
This way if python-base updates, we'll rebuild our python images.

Update FROM lines to use full paths to images.

Change-Id: I554bf07fa8e458e443729cf4b8f40d7ceeaafa04
2019-10-23 17:14:02 +09:00
James E. Blair
31de26ff39 Add jinja-init image jobs
Add jobs to build, upload, and promote a jinja-init image to
Docker Hub.

Change-Id: I493846b672f2a77e63eb78e1fb51c8fefb710990
2019-01-16 11:28:15 -08:00
James E. Blair
9e6a4d327e Remove all docker image building jobs
These will be re-added in followup changes based on the new
zuul-jobs roles.

Change-Id: I0c0691afb180903c573cc1a9eb39590fa58e7ca6
2019-01-16 11:28:07 -08:00
James E. Blair
2059b73584 Fix image promote playbook
This job has no nodes; the playbook needs to run on localhost.
The only tasks use the uri module without local files, so should
be safe.

Change-Id: Ic012426a66be3b85efe9af35089addf1316dfa63
2019-01-11 13:39:07 -08:00
James E. Blair
b4471fb2b6 Fix docker image builds
The credentials secret needs to be associated with the playbook
that uses it.

Also, add build-image-jinja-init to check, this was accidentally
omitted earlier.

Change-Id: I527a26781a716f9307539e4a486d6b79b32f25fd
2019-01-11 12:06:36 -08:00
James E. Blair
83237bc01e Add jinja-init Dockerfile
This creates a jinja-init image based on
https://github.com/ObjectifLibre/jinja-init

We can use this image as an "init container" in k8s to template out
config files using configmaps and secrets.

It also adds a gitea-init Dockerfile, which will require the
jinja-init image to be published first.

Change-Id: I88e14c4f0d868f99aa0a0316e6b9e24c2a8fea68
2019-01-10 10:53:48 -08:00