3 ms·
Only a developer could ask such a question!!!! I'm joking :-P From a sysadmin standpoint sudo is the right choice. Sudo is an established, well defined, (mostl
by atmosx 10y ago
Only a developer could ask such a question!!!! I'm joking :-P
From a sysadmin standpoint sudo is the right choice. Sudo is an established, well defined, (mostly) bug-free program, designed to specifically for that task. It's tool for the job. You can create specific policies[1] keep track of who, what, when, allow this and deny that.
I reckon that this case is a bit tricky though and most people just use sudo to get 'root', so if you're going to do just that, then I guess it's the same.
[1] http://linux.die.net/man/5/sudoers http://linux.die.net/man/5/sudoers
- cyphar 10y ago> I reckon that this case is a bit tricky though and most people just use sudo to get 'root', so if you're going to do just that, then I guess it's the same. sudo is still better in that case, because sudo leaves an audit trail in your system log. Docker doesn't keep a detailed audit log for every request made by a user.
- alrs 10y agohttps://github.com/a2o/snoopy https://github.com/a2o/snoopy