Get Ansible working on an Android phone using a Terminal Emulator like Termux

ansible-termux.sh

#!/data/data/com.termux/files/usr/bin/bash


yes | pkg upgrade && \
yes | pkg install \
    python \
    python-dev \
    libffi \
    libffi-dev \
    openssl \
    openssl-dev \
    libsodium \
    clang \
    cmake
# Install the latest Python package manager.
# The version of pip that comes with Python may be outdated.
pip install --upgrade pip
pip list --outdated --format=freeze | \
    grep -v '^\-e' | \
    cut -d = -f 1 | \
    xargs -n1 pip install -U && \
# The pynacl dependency originally did not install because
# it gave problems building dependencies'
pip install --upgrade pynacl
pip install --upgrade ansible

@lexxxel try add below to your path export RUSTFLAGS="-C lto=n"

@zpyler Thank you very much. By setting this environment variable, I was able to compile the cryptography package and ansible

My environment is slightly different.
I changed:
export CARGO_BUILD_TARGET=aarch64-linux-android
to:
export CARGO_BUILD_TARGET=arm-linux-androideabi
and it installed.
I am unsure if it works correctly. So far all I can do successfully is run the "$: ansible --version" command and I get a number of parameters returned.

I can't use Ansible under termux directly because Ansible tried to use a strange tmp for path:

~ $ ansible -m setup localhost -vvv
...
<127.0.0.1> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo ~u0_a510/.ansible/tmp `"&& mkdir "` echo ~u0_a510/.ansible/tmp/ansible-tmp-1677705385.2093754-32681-130593073141864 `" && echo ansible-tmp-1677705385.2093754-32681-130593073141864="` echo ~u0_a510/.ansible/tmp/ansible-tmp-1677705385.2093754-32681-130593073141864 `" ) && sleep 0'
Using module file /data/data/com.termux/files/usr/lib/python3.11/site-packages/ansible/modules/setup.py
<127.0.0.1> PUT /data/data/com.termux/files/home/.ansible/tmp/ansible-local-32408cvqlt1ww/tmp60urci3t TO /data/.ansible/tmp/ansible-tmp-1677705385.2093754-32681-130593073141864/AnsiballZ_setup.py
<127.0.0.1> EXEC /bin/sh -c 'rm -f -r '"'"'~u0_a510/.ansible/tmp/ansible-tmp-1677705385.2093754-32681-130593073141864/'"'"' > /dev/null 2>&1 && sleep 0'
localhost | FAILED! => {
    "msg": "failed to transfer file to /data/.ansible/tmp/ansible-tmp-1677705385.2093754-32681-130593073141864/AnsiballZ_setup.py: [Errno 2] No such file or directory: b'/data/.ansible/tmp/ansible-tmp-1677705385.2093754-32681-130593073141864/AnsiballZ_setup.py'"
}

/data/.ansible is no valid path to write.

When using proot with Debian:
Most of my ssh connections fail. Some randomly get connected and the result is what is expected. Currently, I'm not able to invest enough time to figure out, what causes the issue.

TL;DR: Ansible under termux is not working on my z fold 4

Instead of export CARGO_BUILD_TARGET I did pkg install binutils

@lexxxel I found that this issue occurs only when using connection: local in the playbook. (which is used by ansible -m ping localhost as well I think)
I guess this is a bug in termux as echo ~u0_a510 is ideally supposed to give /data/data/com.termux/files/home but gives /data. (on linux echo ~username does give /home/username if a user named username exists)

I found two ways of working around it.

• One is to use ssh connection type and pass the localhost/127.0.0.1 from the inventory. (works only for ansible-playbook and doesn't apply for ansible -m setup localhost)
• Or patch ansible code to have this line added. (Works for me both ansible, ansible-playbook commands with connection: local)

diff --git a/plugins/connection/local.py b/plugins/connection/local.py
index 27afd10..e21c4df 100644
--- a/plugins/connection/local.py
+++ b/plugins/connection/local.py
@@ -42,6 +42,7 @@ class Connection(ConnectionBase):

     transport = 'local'
     has_pipelining = True
+    _remote_is_local = True

     def __init__(self, *args, **kwargs):

Related issues, urls

• ansible/ansible#80097 (comment)
• https://superuser.com/questions/484277/get-home-directory-by-username
• https://willthames.github.io/2018/07/01/connection-local-vs-delegate_to-localhost.html

@phanirithvij thank you for your suggestions.
I also tried my production playbook, which uses ssh connections to my proxmox instances. These connections are absolutely instable, like 1 out of 5 work. Which make ansible unusable for me :-(
I will try your fix someday in the next few weeks and post if it helped me.