NOTE:
- Running these Docker images is dependent on a particular user UID on the Docker host. This UID is mapped to an internal user (pulsebuilder) in the image. This was done because the Pulse team does not have root access on the three host VMs. Because of this, and the nature of the Docker daemon running in the root context, pulseui.war (and other artifacts) created by the build would have root-only file level access. Subsequently, we would not be able to delete them from the working directory after execution, e.g. clean up.
As a workaround, a user ID is specified for the docker image at docker image build-time. This same user ID is specified to docker at container run-time. This allows the external user security context to represent (be mapped to) a specific internal security context, which causes all files and artifacts to be written outside of the container with a security context that is not root. The end result is the user which initiated the container can also clean up the local working directory.
TAG Notes:
- The image with pulsebuilder_1.0.0 tag was built with a UID of 185. This UID is for the JBoss user on the DEV, QA, and PROD instances.
- The image with pulsebuilder_1.0.1 tag was built with a UID of 599. This is the UID for the Jenkins user on the master Jenkins SCM server.