Ansible Playbook (Install) Fails

[gibraltarviking]

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]

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]

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

[aarz-snl]

All podman commands must be prefaced by sudo -i

So, sudo -i podman ps

This should work as both the regular user and after running sudo su

You will need to type out the entire command of sudo -i podman ps for both scenarios -- see the install readme for additional commands during install. You should see they all include sudo -i

You could add something like this:

alias podman='sudo -i podman'

to your .bashrc for both accounts which would prevent you from having to type that out every time. But just keep in mind thats required to be typed