Allow Docker Secrets to be used for specifying iDRAC Credentials about docker-idrac6 HOT 4 CLOSED

Good idea. I'm using Kubernetes so secrets are still exposed via environment variables but I will take a look once I got some spare time.

In the meantime you can hide them in a separate .env file instead of your docker-compose and only allow root to access the Docker Daemon and the .env file.

from docker-idrac6.

@brownts I implemented support for Docker secrets for idrac_host, idrac_user, idrac_password and idrac_port.

You can check it out in the docker-secrets branch, just pull image domistyle/idrac6:docker-secrets from Docker Hub. An example docker-compose is available here.

Maybe somebody can give it a try, I have no iDRAC instances running atm.

from docker-idrac6.

@DomiStyle I tested this out and it works great! I hadn't used Docker swarm before and it's required in order to use secrets, so that was a little bit of a stumbling block. The changes you've made to the docker work as expected (although I only used secrets for the "user" and "password", while using the environment variable for the "host" and just defaulting the "port"). I checked this out on a Dell R210ii, R510 and R610...all worked fine. I also used a manually created secret (via "docker secret create ...") as I didn't want them to be stored in a file, thus the reason for the "external" attribute in my configuration below.

I had to adjust my configuration to use the long syntax for the port expose portion of the configuration as it seems by default the ports are not exposed to the host machine when running in a swarm unless you use "host mode" which as far as I can tell is only available in the long syntax, and the long syntax is only available starting with version 3.2.

This is the configuration I tested this with: idrac6_config.txt

Thanks for adding this capability!

from docker-idrac6.

@brownts Thanks for testing! Pulled it into master, should be on Docker Hub in a few minutes.

from docker-idrac6.