sudo , sendmail , and a host of others simply will not start any more.
The mode `777` is actually ***`0`*** `777` .
Among the things in that leading digit are the `setuid` and `setgid` bits.
Most programs which are setuid/setgid have that bit set because
they must run with certain privileges. They're broken now.
Hereās a post I found on the differences between docker --privileged and sudo docker run
ā¦
In an earlier post, someone indicated that docker was not sudo-ed And someone also indicated that QNAP doesnāt have rootā¦
QNAP must have a root user. I donāt know my way around QNAP, but I do know my way around GNU/Linux and various other *nix systems. Root is just another name for āsuperuserā. All *nix OSes have one⦠However, QNAP might not have set a root password and might have the root account mostly disabledā¦
It seems like this problem is limited to QNAP. Iām running Debian and Docker and have not seen this problem. I also set the container with āsudo docker runā ā¦
In any case, for anyone reading this thread:
Please do not change any file permissions to 777
and⦠apparently⦠--privileged is not directly equated to sudo docker run
Forward TCP/28967 toward your Storj node but donāt forward TCP/14002 (the latter should generally only be accessible on your LAN only for you to view the status).