Files
system-config/playbooks/roles/nodepool-launcher/tasks/main.yaml
Clark Boylan f9dd73c2d1 Remove explicit docker-compose install in nodepool-launcher
The nodepool launcher server include the install-docker role which
installs docker-compose via pip then later explicitly installs
docker-compose again with our pip3 role installed pip. These two steps
should be redundant with one another. Now that we're transitioning to
docker compose on Noble we should let install-docker handle this
completely and remove the docker-compose install from nodepool-launcher.

Change-Id: Ibabafd8b5ca26a1ffe04f08996b5fce11980c0a2
2025-01-07 13:14:03 -08:00

52 lines
1.1 KiB
YAML

- name: Copy logging config
copy:
src: logging.conf
dest: /etc/nodepool/launcher-logging.conf
- name: Install apache2
apt:
name:
- apache2
- apache2-utils
state: present
- name: Apache modules
apache2_module:
state: present
name: "{{ item }}"
loop:
- rewrite
- proxy
- proxy_http
- name: Copy apache config
template:
src: launcher.vhost.j2
dest: /etc/apache2/sites-enabled/000-default.conf
owner: root
group: root
mode: 0644
notify: nodepool-launcher Reload apache2
- name: Ensure docker compose dir
file:
state: directory
path: /etc/nodepool-docker
- name: Copy docker compose file
template:
src: docker-compose.yaml.j2
dest: /etc/nodepool-docker/docker-compose.yaml
- name: Update container images
include_tasks: pull.yaml
- name: Start nodepool launcher
include_tasks: start.yaml
# We can prune here as it should leave the "latest" tagged images
# as well as the currently running images.
- name: Run docker prune to cleanup unneeded images
shell:
cmd: docker image prune -f