Closed Freekers closed 3 years ago
I think you might be missing the Docker python SDK:
- hosts: adguard
become: true
vars:
pip_package: python3-pip
pip_install_packages: <---- Add this
- name: docker <---- and this
docker_install_compose: true
docker_users:
- adguard
roles:
- geerlingguy.pip
- geerlingguy.docker_arm
- hosts: adguard
become: true
tasks:
....
This is then installed via the geerlingguy.pip
role.
Thanks for replying, @tgallacher I added both lines, but sadly the issue remains
ansible-playbook playbook.yml --ask-become-pass -vvv
ansible-playbook 2.7.7
config file = /home/pi/ansible-adguard/ansible.cfg
configured module search path = ['/home/pi/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
executable location = /usr/bin/ansible-playbook
python version = 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0]
Using /home/pi/ansible-adguard/ansible.cfg as config file
SUDO password:
/home/pi/ansible-adguard/hosts did not meet host_list requirements, check plugin documentation if this is unexpected
/home/pi/ansible-adguard/hosts did not meet script requirements, check plugin documentation if this is unexpected
Parsed /home/pi/ansible-adguard/hosts inventory source with ini plugin
statically imported: /home/pi/.ansible/roles/geerlingguy.docker_arm/tasks/docker-1809-shim.yml
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
The error appears to have been in '/home/pi/ansible-adguard/playbook.yml': line 217, column 5, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- name: Deploy Stack using Docker Compose
^ here
Ah. I think you might need to use docker_service
instead of docker_compose
; It was renamed in Ansible v2.8, but you appear to be on v2.7.
@tgallacher D'oh, you were right. Thank you!
I'm trying to write a playbook that uses 'docker_compose' as an action in a task in my playbook, but it keeps telling me there is no action detected in the task. The same syntax in combination with your non ARM-docker role which works fine though. Is there a different in syntax on how to use 'docker_compose' as an action in a task for the ARM-docker role compared to the non-ARM docker role?
Steps to reproduce:
Suppose I have the following playbook:
Alongside the following requirements file:
Running
ansible-galaxy install -r requirements.yml --force
outputs:Afterwards, the playbook is run as follows:
ansible-playbook playbook.yml --ask-become-pass -vvv
which gives the following output:Additional debug information from the user that reported this to me: Raspbian GNU/Linux 10 (buster) Docker version 20.10.2, build 2291f61 docker-compose version 1.26.1, build 634eb50
Thank you!