Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Ansible playbook restore_locally.yml errors out #1834

Closed
mattwr18 opened this issue Apr 15, 2024 · 0 comments · Fixed by #1835
Closed

[BUG]: Ansible playbook restore_locally.yml errors out #1834

mattwr18 opened this issue Apr 15, 2024 · 0 comments · Fixed by #1835

Comments

@mattwr18
Copy link
Contributor

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.

  • 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"}

Removing this step, throws the error:

fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "Configuration error - kwargs_from_env() got an unexpected keyword argument 'ssl_version'"}

this is related to #1768

There is now a community.docker.docker_compose_v2 module that we can use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant