exim-relay image pull failure

[mehapps]

Playbook Configuration:

My vars.yml file looks like this:

---
    # The bare domain name which represents your Matrix identity.
    # Matrix user ids for your server will be of the form (`@user:<matrix-domain>`).
    #
    # Note: this playbook does not touch the server referenced here.
    # Installation happens on another server ("matrix.<matrix-domain>").
    #
    # If you've deployed using the wrong domain, you'll have to run the Uninstalling step,
    # because you can't change the Domain after deployment.
    #
    # Example value: example.com
    matrix_domain: mydoman.com

    # The Matrix homeserver software to install.
    # See:
    #  - `roles/custom/matrix-base/defaults/main.yml` for valid options
    # - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choice
    matrix_homeserver_implementation: synapse

    # A secret used as a base, for generating various other secrets.
    # You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
    matrix_homeserver_generic_secret_key: 'hi'

    # Specify reverse proxy
    matrix_playbook_reverse_proxy_type: playbook-managed-traefik

    # Disable the web-secure (port 443) endpoint, which also disables SSL certificate retrieval
    traefik_config_entrypoint_web_secure_enabled: false

    traefik_container_web_host_bind_port: "127.0.0.1:81"
    traefik_config_entrypoint_web_forwardedHeaders_insecure: true
    traefik_additional_entrypoints_auto:
      - name: matrix-federation
        port: 8449
        host_bind_port: "127.0.0.1:8449"
        config: {}

    # Disable integrated Coturn server
    matrix_coturn_enabled: false

    # Disable installing Element
    matrix_client_element_enabled: false

    matrix_playbook_docker_installation_enabled: false

    # A Postgres password to use for the superuser Postgres user (called `matrix` by default).
    #
    # The playbook creates additional Postgres users and databases (one for each enabled service)
    # using this superuser account.
    postgres_connection_password: 'hi'

    matrix_appservice_double_puppet_enabled: true
    matrix_synapse_ext_password_provider_shared_secret_auth_enabled: true
    # matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret: YOUR_SHARED_SECRET_GOES_HERE
    matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret: hi2

    matrix_bridges_encryption_enabled: true
    matrix_bridges_encryption_default: true

    matrix_mautrix_discord_enabled: true
    matrix_mautrix_slack_enabled: true
    matrix_mautrix_signal_enabled: true
    matrix_mautrix_whatsapp_enabled: true
    matrix_synapse_configuration_extension_yaml: |
      experimental_features:
        msc2716_enabled: true
    matrix_mautrix_whatsapp_configuration_extension_yaml:
      bridge:
        history_sync:
          backfill: true
    matrix_mautrix_meta_instagram_enabled: true
    matrix_beeper_linkedin_enabled: true
    matrix_go_skype_bridge_enabled: true

Matrix Server:

• OS: Ubuntu 22.04
• Architecture: amd64

Ansible:
If your problem appears to be with Ansible, tell us:

• where you run Ansible: Mac with MacOS 15 Sequoia
• what version of Ansible you're running: core 2.18.1

Problem description:

Describe what you're doing, what you expect to happen and what happens instead here.
Tell us what you've tried and what you're aiming to achieve.

I run just update, then ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start. I get this error at the very end.

TASK [galaxy/exim_relay : Ensure exim-relay image is pulled] *******************
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (10 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (9 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (8 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (7 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (6 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (5 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (4 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (3 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (2 retries left).
FAILED - RETRYING: [matrix.mydomain.com]: Ensure exim-relay image is pulled (1 retries left).
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ModuleNotFoundError: No module named 'requests'
fatal: [matrix.mehapps.com]: FAILED! => changed=false
  attempts: 10
  msg: Failed to import the required Python library (requests) on server's Python /usr/local/bin/python3.11. Please read the module documentation and install it in the appropriate location. If the required library is installed, but Ansible is using the wrong Python interpreter, please consult the documentation on ansible_python_interpreter

PLAY RECAP *********************************************************************
matrix.mydomain.com         : ok=53   changed=1    unreachable=0    failed=1    skipped=70   rescued=0    ignored=0

Additional context
I used this guide

[spantaleev]

The error was: ModuleNotFoundError: No module named 'requests'

Your Ansible setup seems broken. It appears that the Python requests library is not available alongside Ansible.

[mehapps]

I noticed that error so I installed it on my local and server machine but it throws the same error

[joolsr]

I get a related error when running setup on newly installed Ubuntu 24.10 server. Again when trying to get Exim pulled. This is with the quick start set-up, nothing special. Seems the two are linked docker/docker-py#3256. This was fixed last year, so not sure why we're seeing these similar issues again.

[Graxo]

When pulling it outside of the playbook it runs normal:

Using default tag: latest
latest: Pulling from devture/exim-relay
Digest: sha256:857f15c631a9a58b0585b2caa56d3622ecf7c7339849f1d8c0871102729e3541
Status: Image is up to date for devture/exim-relay:latest
docker.io/devture/exim-relay:latest
[graxo@matrix]$```

But the playbook doesnt see that or something.
Im using CentOS Stream 9

[spantaleev]

It's not a problem with the container image, but rather with Ansible and its modules (which depend on other Python libraries like request or the Docker-Python SDK).

Try installing/upgrading Ansible or running it in a container, where you'll get a recent and proper installation. See docs/ansible.md for more details.

[Graxo]

Its a fresh vm install with the newest version of ansible. When i check if requests is installed with pip3 it (also) doesnt update and says its up to date.

To install Ansible, i did dnf install ansible
Ill check some documentation again.

[root@matrix files]# ansible --version
ansible [core 2.14.18]
  config file = /opt/matrix/files/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.9/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /bin/ansible
  python version = 3.9.21 (main, Dec  4 2024, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] (/usr/bin/python3)
  jinja version = 3.1.2
  libyaml = True

root@matrix matrix]# pipx install requests
'requests' already seems to be installed. Not modifying existing installation in '/root/.local/pipx/venvs/requests'. Pass '--force' to force installation.

EDIT: Using Ansible in Docker it worked fine. Ill use that for now.