Storage location in file system

[ldillon59102]

Your documentation states that LME requires at least 128GB of storage. Where on the files system will the bulk of the data be stored?

[jparsonstf]

LME sets up pods which store their volumes in location (by default): /var/lib/containers

[ldillon59102]

Thanks for the reply. I take it this has no problem traversing symlinks?

[cbaxley]

If you set up a symlink from /var/lib/containers to your other volume before installing, it should work. If you have problems, you could actually edit the install_lme_local.yml script and change where it stores the volumes. Look for the setup global overlay-fs usage section. Thanks, Clint Baxley

…

On Tue, Feb 4, 2025 at 4:53 PM ldillon59102 ***@***.***> wrote: Thanks for the reply. I take it this has no problem traversing symlinks? — Reply to this email directly, view it on GitHub <#558 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQY33VQSQFYOOINLUYBNMT2OEZD5AVCNFSM6AAAAABWGES6YCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBWGAYTOOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ldillon59102]

What we typically do, on a server that has a data storage need, is do a mirror pair for the root and a ZFS pool for the data. It's usually better to leave the configuration as stock as possible and just symlink from the root file system to the ZFS pool. In this way, if the configuration file gets overwritten in an update, it should still work. But every once in a while, I find a product that doesn't work with symlinks, so better to ask. We are hopefully moving off systemd-journal-upload for our logs. It's one of those products that does not properly work with symlinks.

[aarz-snl]

symlinks should work as long as there nothing unique to your network that may cause an issue like selinux or some other type of permissions issues

[aarz-snl]

need to ensure all permissions lineup too with what already exists - permissions get buil tin during the ansible playbook that'll need to exist

[jparsonstf]

BTW - When you want to move some volumes (even empty ones; like lme_backups initially) to another drive using symlinks (or mountpoints) it is necessary to restart the container. Thought since it was empty and unused, I could move it around and magic, but no. Did get to deep dive into podman at least.

[aarz-snl]

and for restarting you can use:

sudo systemctl restart lme.service

to restart all containers

Or

something like:

sudo systemctl restart lme-fleet-server.service to restart a single container. Change service name as needed