mirror of
https://github.com/moghtech/komodo.git
synced 2025-12-05 19:17:36 -06:00
How to configure Komodo Deployments Volumes as absolute or relative paths?
#427
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aaro-n on GitHub (Jun 15, 2025).
Problem description
Using komodo's Deployments to deploy the paradedb image, I need to map the
/var/lib/postgresql/datain the container to the/home/www/komodo-data/data/postgresqlon the host. In the Volumes item, I configure/home/www/komodo-data/data/postgresql:/var/lib/postgresql/data. The/home/www/komodo-data/data/postgresqlfolder will be created by itself, but the container cannot run.How to configure
postgresql:/var/lib/postgresql/datato run normally, but I need to map the data to an absolute path.Log
End
Komodo 1.18.1 komodo-periphery latest version, I have checked the documentation and searched for the problem, but no solution was found, or the keywords I searched were wrong?
@mbecker20 commented on GitHub (Aug 28, 2025):
The absolute mount is correct, however if you run Periphery in container, Periphery also needs to be given 1:1 mount inside and outside container in order to work correctly, like is documented for PERIPHERY_ROOT_DIRECTORY. If you can switch to systemd Periphery, it would also fix the issue.