search

ManageIQ / manageiq

ManageIQ Open-Source Management Platform
https://manageiq.org
Apache License 2.0
1.34k stars 896 forks source link

ManageIQ Workflows Appliance Image Registry #22640

Open agrare opened 1 year ago

agrare commented 1 year ago

When using podman as a non-root user (aka the manageiq user on an appliance), podman uses rootless_storage_path = "$HOME/.local/share/containers/storage" to store images.

On an appliance lv_home is only 1GB so you cannot keep many images here. You can control where images are stored for a user with a ~/.config/containers/storage.conf file, e.g.:

# cat /home/manageiq/.config/containers/storage.conf 
[storage]
  driver = "overlay"
  graphroot = "/var/www/miq/vmdb/tmp/containers"
[storage.options.overlay]
  ignore_chown_errors = "true"

We should pick a location to store these images that isn't on a small volume plus document it so users can resize the logical volumes if they want to.

https://github.com/ManageIQ/manageiq/issues/22311

Fryguy commented 1 year ago

@bdunne Would like your thoughts/opinions here.

Fryguy commented 1 year ago

IMO I think we need a new, dedicated volume, but I'm not sure how that would work with upgrades.

agrare commented 1 year ago

Without free space on the volume group we couldn't carve out another logical volume and shrinking lvs isn't practical ...

I agree that would be ideal though. We could add something to appliance console to let a user attach another disk and configure it for them but default to it being on the data volume

agrare commented 1 year ago

Add the options to the podman runner to change the root image directory from $HOME/.local/share/containers/storage to /var/www/miq/vmdb/data/containers/storage

miq-bot commented 10 months ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot commented 7 months ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot commented 3 months ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot commented 2 weeks ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.