Add SELinux support and fix IPv6 issues for containerized qlever commands#273
Open
tanmay-9 wants to merge 12 commits intoqlever-dev:mainfrom
Open
Add SELinux support and fix IPv6 issues for containerized qlever commands#273tanmay-9 wants to merge 12 commits intoqlever-dev:mainfrom
tanmay-9 wants to merge 12 commits intoqlever-dev:mainfrom
Conversation
tanmay-9
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
DISABLE_SELINUXoption: On systems with SELinux enforcing (e.g. Fedora, RHEL), containerized qlever commands can fail with permission errors on bind-mounted files. A newDISABLE_SELINUX = yesoption in the[runtime]section of theQleverfile(or--disable-selinux yeson the command line) resolves this. It applies to all containerized commands with volume mounts:index,start,add-text-index,system-info, andui.DISABLE_SELINUXis not set, so that the user knows thatDISABLE_SELINUXneeds to be set toyesin order for commands to work.HOST_NAMEresolves to IPv6 first, since container port forwarding typically only listens on IPv4. The warning suggests using an explicit IPv4 address like 127.0.0.1.Fixes SELinux permissions with Podman containers #220