Option to disable uid=0 check
See original GitHub issueInside Docker containers it’s often unavoidable/necessary to run processes as uid 0 but this module stubbornly refuses to run as uid 0.
I’ve monkey-patched the module to remove that check and everything seems to work fine so far so I’d suggest having an option like --allow-root
or better yet, remove this opinionated check.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Lowest UID 0 is less than 1 Error - BitTitan Help Center
You may disable validation of UIDs: Sign in to your MigrationWiz account; Click on Mailbox Migration. Click on Migrate Mailbox. Select your ...
Read more >usr/bin/sudo must be owned by uid 0 and have the setuid bit set
go to recovery mode by keep pressing Esc while booting the system. select root option in long list you can see after entering...
Read more >Linux sysadmin basics: User account management with UIDs ...
The root account has the awesome privilege of having UID = 0 and GID ... To further test this assertion, assign a test...
Read more >vserver services access-check authentication translate
Examples. This example translates the UNIX UID 0 to username "root" on node "node2" for Vserver "vs1.".
Read more >capabilities(7) - Linux manual page - man7.org
Privileged processes bypass all kernel permission checks, ... flags that can be used to disable special handling of capabilities for UID 0 (root)....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It will refuse to run inside Docker as root at all with the
Must drop privileges
error. After I patched out that check, it runs just fine.I run snmpsim inside a CI environment which always runs its jobs as uid=0 and I tried the
--process-user=nobody
and--process-group=nogroup
arguments but then I ran into tempfiles permission errors (presumably fixed by https://github.com/etingof/snmpsim/commit/e9e1d5b8103cbe93f474de6e4a952dac7d06f41d but not released), so I gave up and patched out that check.I agree with silverwind, the workaround is completely non-obvious, who would have thought you can provide root to process-user. I’ve spent a day messing with the permissions until i stumbled upon this issue.