-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Regression: Run as user nobody:nogroup was broken in logstash:7.17.8 (logstash:7.17.7 works as expected) #14836
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
Comments
Found the issue - in backtrace
The file to load that fails logstash/build.rb not logstash/build The Permissions for the following file had been changed from 7.17.7 -> 7.17.8
Currently we have patched our docker image from docker.elastic.co/logstash/logstash:7.17.8 with the following changes, and all works - So there is your Fix :slight_smile: Dockerfile
NOTE: I have also verified that this issue ALSO exists with 8.6.0 - So I assume any changes to 8.x since Nov 30 16:11 also has the same issue - Please make the same change in the 8.x Branch |
The same issue was found in 8.5.1 but not in 8.5.0 |
The fix will be update |
btw, I have tested locally with v8.5.0 and run the docker image build process, but the build.rb is missing read permission. |
Logstash information:
Plugins installed: (
bin/logstash-plugin list --verbose
)AS in from docker image:
JVM (e.g.
java -version
):OS version (
uname -a
if on a Unix-like system):Any Linux version - tested on the following
Description of the problem including expected versus actual behavior:
Steps to reproduce:
Success with 7.17.7
Failure with 7.17.8
7.17.8 Failure - using nobody:nogroup
Success with 7.17.7 - using nobody:nogroup - CTRL-C to stop
Running 7.17.8 as root works - no need to show full output (same as with 7.17.7)
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: