Skip to main content

Configuring a volume for Save to File System (Linux w/ Docker)

On a Docker deployment, the Save to File System Job action writes files inside the Informer containers. To make those files available on the host (so other tools can use them), each Informer container needs a volume mount to the host's file system. The export is not static: it writes to whichever Informer container runs the action.

Add the volume mount​

  1. Stop all Informer components:

    docker-compose stop

  2. Delete the current Informer containers (default naming shown):

    docker-compose rm informer-api
    docker-compose rm informer-query
    docker-compose rm informer-schedules

  3. Add this line to the volumes section of every Informer service in docker-compose.yml:

    - ./joboutput:/etc/joboutput
    • Left of the colon, ./joboutput is the host directory where exports land (this creates a joboutput directory in the Informer install root). The name is up to you; joboutput is a sensible default.
    • Right of the colon, /etc/joboutput is where the Save to File System action writes inside the container. The container path must start with /etc (which always exists); the subdirectory after it is customizable.

    Each Informer container's volumes then looks like:

    volumes:
      - ./plugins:/informer/plugins
      - ./java/plugins:/informer/java/plugins
      - ./config.json:/informer/config.json
      - ./joboutput:/etc/joboutput

  4. Save and start all Informer components:

    docker-compose up -d

In Informer, the directory path for the Save to File System Job action is /etc/joboutput. Test the action and confirm the export writes to the host's ./joboutput directory. See Save to File System for more on the action itself.