Closed conorpp closed 5 years ago
That, or there's an existing mechanism to override the warning: sudo ALLOW_ROOT= /path/to/solo
. What do you think about adding this info to the (aborting) warning, and also to the Docker build script?
I'd also be fine with just outputting a warning and continuing.
I think the warning is easiest. I think the only reason we put the sudo restriction in there was to catch udev issues, and I think a warning would still catch it fine.
When making a bundled firmware in Docker, it runs into this issue.
Maybe turn the root message into a warning?