feat: add IPFS_PROFILE to fix VPS NetScan abuse #1249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref: ipfs/kubo#8585 (comment)
Result:

(1) left:v0.14.0 right:v0.14.0+
IPFS_PROFILE=server
It can be found from the log that after adding the environment variable, the scanning of the internal network was reduced.
(2)v0.14.0+

IPFS_PROFILE=server
restart ipfs dockerleft: restart right: first time start
It can be found that after the restart, the internal network scanning situation is as expected.