cssdemo/agentcontainer repository overview

⁠THIS IS A WORK IN PROGRESS AND NOT A FINAL VERSION AND IS NOT INTENDED FOR DISTRIBUTION

⁠To run in background (note the -d AND the -t):

docker run --dns=192.168.58.50 -d -t -e "cmsusername=demouser" -e "cmsdomain=demo" -e "cmspassword=password" -e "cmsserver=cms.demo.lab" -e "ssl=yes" -e "sslresponse=/app/javaAgent/test/RootCA.cer" -v /home/demo/Documents/certs:/app/javaAgent/test cssdemo/agentcontainer

⁠To run in the foreground:

docker run --dns=192.168.58.50 -it -e "cmsusername=demouser" -e "cmsdomain=demo" -e "cmspassword=Cheese33" -e "cmsserver=cms.demo.lab" -e "ssl=yes" -e "sslresponse=/app/javaAgent/test/RootCA.cer" -v /home/demo/Documents/certs:/app/javaAgent/test cssdemo/agentcontainer

⁠Notes:

The --dns is so that the DNS of the container is overridden. The containers default DNS goes out to google. The DNS address should be the DNS server inside the environment that knows where CMS is. If we are using SSL, we should not connect via IP as the certificate would not match. In my environment 192.168.58.50 is my AD DC, which knows about my CMS box.

The -e specifies a variable that will be passed into the docker container. The variables that need to be specified are: cmsusername, cmsdomain, cmspassword, cmsserver, ssl, sslresponse. They will replace everything in the answers file that the Java Agent needs to conenct to CMS. If all of these variables are not specified, the Java Agent will not successfully connect to CMS.

The -v is how we share a directory and its contents from our host machine into the container. The format is {host location}:{container location}, where the location is a directory and not a specific file. If we are connecting the Java Agent to CMS via SSL, we need to specify a host location with a trusted root cert from the CA that issued the CMS cert. We would also need to make sure the sslresponse variable looks like: -e "sslresponse={container location}/{RootCert}".