I have been using a standard user account to start the IPFS daemon without any issues so far, but I’m running into problems now that I’m experimenting with private IPFS networks (and then on to ipfs-cluster).
It may be due to not being careful as I switch between running sudo vs user commands (need root for systemd), but thought I’d ask:
Q1: Should the daemon be run as root for better security?
Since I’ve installed public ipfs nodes as std user and seen no issues, I know it’s possible to run as a std user, but is that best practice?
Q2: Is there any reason a private network IPFS installation requires root?
Q3: Is there any reason an ipfs-cluster installation requires root?
Q1 is main question, as I am doubtful root is required.
Not sure about the answers to questions Q2 & Q3, but I’ve spoken with several others that always run their IPFS nodes as a std user.
After chown -R acct.acct /home/acct all “anomalies” went away except for the webui on port 5001, which I can’t get working in the private network configuration, tho I fully tested the installation (from the base ipfs install) while configures as a normal public ipfs node.
Q1: Should the daemon be run as root for better security?
I wouldn’t. I recommend running it as your user or as a special “ipfs” user.
Q2: Is there any reason a private network IPFS installation requires root?
It doesn’t.
Q3: Is there any reason an ipfs-cluster installation requires root?
It shouldn’t.
webui
Answered in Webui not working in private network configuration