Open etlweather opened 8 years ago
Thanks for your suggestion. I choose to add credentials in ENVs for not constrain the use of this container in rancher (so you can also start it in a local docker installation).
If you want, you can make a PR for check existance of both modes.
See http://docs.rancher.com/rancher/latest/en/rancher-services/service-accounts/
By setting the following labels on the service:
The container will be started by Rancher with the following environment variables:
Which makes it that you don't have to hard code the credentials when creating the service.