Run docker-compose pull before docker-compose up

This will make sure that the latest relevant images are in the
local image storage, and therefore, will cause docker-compose up
to recreate containers when the images are updated.

Change-Id: Ic6f0bc8c8aea5b5c16501f4ab5d3095fb70c0ff7

playbooks/roles/gitea/tasks/main.yaml

@@ -37,6 +37,10 @@
     name:
       - docker-compose
     state: present
+- name: Run docker-compose pull
+  shell:
+    cmd: docker-compose pull
+    chdir: /etc/gitea-docker/
 - name: Run docker-compose up
   shell:
     cmd: docker-compose up -d

playbooks/roles/haproxy/tasks/main.yaml

@@ -20,6 +20,10 @@
     name:
       - docker-compose
     state: present
+- name: Run docker-compose pull
+  shell:
+    cmd: docker-compose pull
+    chdir: /etc/haproxy-docker/
 - name: Run docker-compose up
   shell:
     cmd: docker-compose up -d

playbooks/roles/registry/tasks/main.yaml

@@ -36,6 +36,10 @@
     name:
       - docker-compose
     state: present
+- name: Run docker-compose pull
+  shell:
+    cmd: docker-compose pull
+    chdir: /etc/registry-docker/
 - name: Run docker-compose up
   shell:
     cmd: docker-compose up -d

playbooks/roles/zuul-preview/tasks/main.yaml

@@ -7,6 +7,10 @@
     name:
       - docker-compose
     state: present
+- name: Run docker-compose pull
+  shell:
+    cmd: docker-compose pull
+    chdir: /etc/zuul-preview-docker/
 - name: Run docker-compose up
   shell:
     cmd: docker-compose up -d