Closed angelmadames closed 1 year ago
I think that a previous problem (of ansible-lint installing a newer version of ansible) has raised its head again. Trapped in dependency hell. I will look to resolve this, thanks for reporting.
@angelmadames do you want to have a test again? I seem to be able to get ansible-galaxy to work on 2.12.9 now.
docker run --rm -it willhallonline/ansible:2.12-alpine-3.14 /bin/ash
...
/ansible # ansible --version
ansible [core 2.12.9]
config file = None
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 = /usr/bin/ansible
python version = 3.9.16 (main, Dec 10 2022, 13:47:19) [GCC 10.3.1 20210424]
jinja version = 3.1.2
libyaml = False
/ansible # ansible-galaxy install willhallonline.acme_sh
Starting galaxy role install process
- downloading role 'acme_sh', owned by willhallonline
- downloading role from https://github.com/willhallonline/ansible-role-acme_sh/archive/master.tar.gz
- extracting willhallonline.acme_sh to /root/.ansible/roles/willhallonline.acme_sh
- willhallonline.acme_sh (master) was installed successfully
Closing as stale and probably resolved by previous updates.
Just a note that I'm getting this error with versions:
docker run --rm -it -v $(pwd):/ansible \
-v ~/.ssh/id_rsa:/root/.ssh/id_rsa -v ~/.ssh/known_hosts:/root/.ssh/known_hosts \
-v $(pwd)/vault_pass.txt:/root/.ansible_vault_pass.txt -v ~/ansible-roles-ext:/root/ansible-roles-ext \
-v ~/ansible-collections-ext:/root/ansible-collections-ext \
willhallonline/ansible:2.14-alpine-3.18 \
ansible-galaxy collection install --force -r requirements.yml --collections-path /root/ansible-collections-ext
10:37:51 Starting galaxy collection install process
10:37:52 Process install dependency map
10:37:52 ERROR! ansible-galaxy requires resolvelib<0.9.0,>=0.5.3
Got it to work OK with 2.12-alpine-3.18.
Summary
Some images with 2.12 and Alpine 3.14 (and above) are throwing the error:
This seems to be happening starting yesterday (Feb 20, 2023) after the image update in Docker Hub.