docker: allow IPFS_PROFILE to choose the profile for ipfs init

[akaihola]

Added support for an IPFS_PROFILE environment variable in the bin/container_daemon. The variable, if present, is used with ipfs init to add a --profile=$IPFS_PROFILE argument which will apply to chosen profile to the newly created configuration.

This is useful for automatic IPFS deployments in hosted container environments, e.g. Kubernetes. In such situations, it's essential to use --profile=server.

Pull request helm/charts#7746 requires this change in order to add the profile configurable parameter to the IPFS Helm chart.

[akaihola]

It seems GitCop rejected my commit message as invalid, but I can't find the guidelines for commit messages. My message is 64 characters long, so that shouldn't be the issue. Advice, anyone?

[rob-deutsch]

@akaihola guidance is here: https://github.com/ipfs/go-ipfs/blob/master/contribute.md

The commit message is missing the trailers.

[akaihola]

@rob-deutsch, thanks for your explanation and sorry for missing those instructions.

I now corrected the commit message and force pushed the branch.

bash is fun

[Stebalien]

This may not be necessary, but I can never remember the precise rules.

[Stebalien]

Let's quote this. That is, INIT_ARGS="...".

[funkyfuture]

@Stebalien afaict, your remaining concern has been resolved (it is marked as outdated in the view), and you might approve this now.

[Stebalien]

@whyrusleeping @lgierth any objections?

[whyrusleeping]

Just for the docker stuff? Seems fine to me

[Kubuxu]

SGMT.
It will do until we need to pass more things as INIT_ARGS and then we can use bash's array syntax.

[victorb]

Any chance of merging this? Makes infra a lot simpler (no need to have a separate Dockerfile to just override the profile), seems straightforward and been approved.