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

Ansible Playbook (Install) Fails #546

Open
gibraltarviking opened this issue Jan 8, 2025 · 2 comments
Open

Ansible Playbook (Install) Fails #546

gibraltarviking opened this issue Jan 8, 2025 · 2 comments

Comments

@gibraltarviking
Copy link

Really struggling with LME v2.0. The first ansible playbook is consistently failing to install podman and the corresponding containers. Over a week I have made a dozen attempts to install LME to a clean installation of Ubuntu Server 22.04.5.

To recap steps taken

Install Ubuntu 22.04.05 to a new VM that has 16GB RAM, 8 CPU and 1TB storage
update apt
install curl jq unzip
use curl to fetch files from github, expand into ~/LME
use touch to create ~/LME/config/lme-environment.env, then copy contents of ~/LME/config/example.env to lme-environment.env
edit lme-environment.env, update IPVAR to reflect IPv4 address that is assigned to ens160
install ansible
run ansible playbook as normal user: ansible-playbook -K ./ansible/install_lme_local.yml

After ansible completes I try to use podman ps to check status of containers. every single time I do so I am informed that podman is not installed. After installing podman using apt I discover there are no containers installed

Any idea what I'm doing wrong?

Thank you

@cbaxley
Copy link
Collaborator

cbaxley commented Jan 8, 2025

Yes. You can run podman as root (sudo su) and source the ~/.profile file like this:

. ~/.profile

There is a . in there that you need to put on the command line as well. It means to source the file.
Then you should be able to run podman ps

@gibraltarviking
Copy link
Author

Hi Clint,

Thank you for your reply.

Apologies if I don't understand your answer. I stated that the Ansible script failed to install podman and the associated containers.

Steps taken - per your suggestion I ran these commands in order shown
sudo su
. ~/.profile
podman ps

Results show no containers are present.

Per your comment about sourcing the profile, are you suggesting that I should have "sourced profile" immediately after running the ansible playbook to install LME, and if I had done so I would have seen the containers?

Thank you

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

No branches or pull requests

2 participants