-
|
In a very basic setup, we fail to deploy a PostgreSQL 17 cluster from pigsty 3.7.0 because of It looks like pigsty brought it's own python3.12 and uses it instead of whatever python was shipped with the OS. But we can't install python3-dnf to that python3.12 because that specific module can only work with system python, which is 3.6.8 (ant best 3.9 if we go with RHEL9). I was under the imperssion that there is no need to tweak pigsty's playbooks and inventories other that main How should we navigate this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
|
The issue is caused by recent changes in linux upstream packages. My guess is that installing it via python3.12 -m pip should resolve the problem. Since EL10 already provides official support and EL8 doesn’t support io_uring, we’re planning to drop EL8 support in the next release. So the simplest solution—if it’s an option for you—is to switch to EL10 or EL9. (or debian / ubuntu) |
Beta Was this translation helpful? Give feedback.
More specific it was https://doc.pgsty.com/install/offline/#offline-package
that helped. Wasn't clear that after offline installation of pigsty I just needed to set
repo_enabled: trueandnode_repo_modules: local.Thank you!
I switched to Rocky 9.7 everywhere now. So I'm fixing the title.