michaeljmarshall commented on pull request #8796: URL: https://github.com/apache/pulsar/pull/8796#issuecomment-752785842
After digging into this morning's test failures, I can see that the tests failed because we're using `supervisord` to spawn the pulsar processes (broker, bookie, etc.) and our configuration script needed permission to edit `supervisord` configuration files. My latest commit updates the docker image used to run tests (`pulsar-test-latest-version`) so that the container runs as the root user, `supervisord` runs as root, and `supervisord` will spawn pulsar components as the pulsar user. I am slightly concerned that this approach requires configuration in multiple places (each of the pulsar component `conf` files) to maintain the correctness of the tests. Given that new components are likely rare, I think it should be simple enough to maintain, but I want to call this risk out. The risk is that a new test could accidentally run as root and work because it somehow relies on running as root. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
