Isn't winrm a typical way to access Windows targets with ansible? I had to use the community-ee-base image like this to get it to work with my Windows-based targets, pip installing pywinrm before running ansible-playbook:
podman run --rm --userns=keep-id -u $(id -u):$(id -g) \
-w "$PWD" -v "$PWD:$PWD:Z" \
-e ANSIBLE_FORCE_COLOR=0 \
ghcr.io/ansible-community/community-ee-base:2.20.0-1 \
bash -lc "python3 -m pip install --no-cache-dir --target /tmp/pip pywinrm && \
PYTHONPATH=/tmp/pip ansible-playbook -i inventory.yml playbook.yml"
Isn't winrm a typical way to access Windows targets with ansible? I had to use the community-ee-base image like this to get it to work with my Windows-based targets, pip installing pywinrm before running ansible-playbook: