-
Notifications
You must be signed in to change notification settings - Fork 0
Reductionist non-privileged installation process #98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Podman - change Ansible collection from community.docker to containers.podman - update all Ansible tasks to use podman instead of docker, we install podman-docker for a docker compatible CLI but we need to be podman specific in our Ansible playbook - move group_vars/reductionist -> group_vars/all so all "reductionist_" prefixed vars can be used across plays, specifically Step and Reductionist - update documentation
…ged user account that'll be running the Reductionist, and any other, containers. We need linger enabled for the podman process to continue running after the user's logged out of the session. Deployment documentation updated.
Reductionist can be used with https, either with the optional Ansible playbook Step deployment or with third party certificates. Documentation updated for installation of 3rd party certificates.
sd109
requested changes
Mar 17, 2025
Could you have a go at fixing the CI failures too please? |
We're still seeing: WARNING Ignored exception from ArgsRule.matchtasks while processing deployment/site.yml (playbook): 'force_restart' There's an ansible bug ticket for this diagnostic. Trying a commit to see if lint passes as is.
Github file descriptor limit: "[ALERT] (1) : [haproxy.main()] Cannot raise FD limit to 80027, limit is 65536."
2184f67
to
69f8984
Compare
…4.04 and it looks like somebody's already been scoping this out in the branch update/python-deps. Testing...
sd109
reviewed
Mar 17, 2025
sd109
reviewed
Mar 17, 2025
sd109
approved these changes
Mar 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Ansible deployment to allow for unprivileged deployment using Podman: