Question: Why /opt/vectr/user is not using NAMED VOLUMES in docker-compose.yml (v8.0.2)?

[ferozbasir]

Hi Team,

I've just realized under vectr-tomcat container setting in docker-compose.yml (v8.0.2), /opt/vectr/user is not using NAMED VOLUMES rather it sets to use BIND-MOUNT instead. Any reason behind it as I thought we are moving away from BIND-MOUNT mechanism?

vectr-tomcat: image: securityriskadvisors/vectr_tomcat:8.0.2 networks: vectr_bridge: aliases:

• ${VECTR_HOSTNAME} volumes:

  - ./resources:/opt/vectr/resources

  • vectr-resources:/opt/vectr/resources **- ./user:/opt/vectr/user

    - vectr-user:/opt/vectr/user**

    - ./logs:/usr/local/tomcat/logs

  • vectr-logs:/usr/local/tomcat/logs
  • builder-runtimes:/opt/vectr/rta env_file:
  • ./.env ports:
  • "${VECTR_PORT:-8081}:8443" restart: unless-stopped depends_on:
  • vectr-mongo

Thanks.

[thebleucheese]

You can change that to use volumes but users specifying an existing ssl cert from the container host should use the bind mount so the container sees it on startup. We haven’t adjusted the user-specified cert code path that runs on container startup to work with volume mounts yet so we had to leave that one.

[ferozbasir]

Well noted.

Thank you.