The test was incorrectly using 'docker exec id -u' which always returns
the container's original user context, not the user that the entrypoint
switched to.
Key insights:
- docker exec creates NEW processes with the container's user context
- When container starts with --user root, docker exec runs as root
- The entrypoint correctly switches the MAIN process to nodejs user
- We need to check the actual n8n-mcp process, not docker exec sessions
Changes:
- Check the actual n8n-mcp process user via ps aux
- Parse the process owner from the ps output
- Added demonstration test showing docker exec vs main process users
- Added clear comments explaining this Docker behavior
This correctly verifies that the entrypoint switches the main application
process to the nodejs user for security, which is what actually matters.
13591df47c