I’m interested in the user running a mesos task on a slave. The `switch_user` flag says:
--[no-]switch_user Whether to run tasks as the user who submitted them rather than the user running the slave (requires setuid permission) (default: true) Now, from experiments, and from what I read in : https://github.com/apache/mesos/blob/master/src/slave/containerizer/fetcher.cpp If you run with —switch-user, or with the default configuration, mesos runs the task on the slave based on the *username* reported by the framework. I would have expected, in the Unix world, mesos would choose to go with to the *userid* detected from the framework. It is indeed the more portable option IIUC: - under a unix, two users declared with distinct names and the same userid are aliases of each other, - following the userid is standard practice in cross-network applications (e.g. ssh) Why the username ? — FG
