AnsweredAssumed Answered


Question asked by ryanvictory on Apr 12, 2017
Latest reply on Apr 14, 2017 by trichmond
Branched to a new discussion

We are evaluating the MapR PACC and found a bug in the way it handles Ticketfiles for secure clusters. Following the documentation (Running the Application Container Based on the MapR PACC ), we are setting the MAPR_TICKETFILE_LOCATION environmental variable to point to the MapR client ticket (which we have placed into the docker container via a Docker volume mount using -v on the command line). What we have noticed, however, is that the /opt/mapr/installer/docker script (or perhaps another script it calls) is defining MAPR_TICKET_FILE incorrectly no matter what is placed into MAPR_TICKETFILE_LOCATION. For example:

  1. We set MAPR_TICKETFILE_LOCATION=/opt/mapr_tickets/mapr_ticket
  2. We use volume binding to add the ticket file to the container (in /opt/mapr_tickets)
  3. We run the container, MapR sets the MAPR_TICKETFILE variable to /tmp/mapr_ticket

Clearly this is a bug, I'm not sure if testing wasn't done outside of /tmp because even the docs only show an example using /tmp. In this case, why have MAPR_TICKETFILE_LOCATION at all?