You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reproduce this, you must have a backup of an instance locally in the ansible/backups directory. This is stored when running the playbook ansible/backup.yml.
With a local backup, run the playbook:
ansible-playbook ansible/restore_locally.yml
After choosing a playbook, you will encounter an error trying to use pip install docker-compose:
atal: [127.0.0.1]: FAILED! => {"changed": false, "cmd": ["/usr/bin/python", "-m", "pip.__main__", "install", "docker-compose"], "msg": "\n:stderr: error: externally-managed-environment\n\n× This environment is externally managed\n╰─> To install Python packages system-wide, try 'pacman -S\n python-xyz', where xyz is the package you are trying to\n install.\n \n If you wish to install a non-Arch-packaged Python package,\n create a virtual environment using 'python -m venv path/to/venv'.\n Then use path/to/venv/bin/python and path/to/venv/bin/pip.\n \n If you wish to install a non-Arch packaged Python application,\n it may be easiest to use 'pipx install xyz', which will manage a\n virtual environment for you. Make sure you have python-pipx\n installed via pacman.\n\nnote: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.\nhint: See PEP 668 for the detailed specification.\n"}
Steps to reproduce.
To reproduce this, you must have a backup of an instance locally in the ansible/backups directory. This is stored when running the playbook ansible/backup.yml.
Removing this step, throws the error:
this is related to #1768
There is now a
community.docker.docker_compose_v2
module that we can use.The text was updated successfully, but these errors were encountered: