Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-4695

Expand instanceIds in volume configuration

    Details

    • Type: Task
    • Status: Accepted
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage Volumes
    • Labels:
      None

      Description

      (oirginal title: Dynamic Volume for Logging)

      Hi
      In my application the logs will be written to a specific folder in the file system. Please find below the mounting of volume which is working for me.

      "volumes": [

      { "containerPath": "/var/log", "hostPath": "/var/log", "mode": "RW" }

      I need to specify a folder inside /var/log with container ID and get the logs written there to avoid conflict from multiple containers in the same host.

      "volumes": [

      { "containerPath": "/var/log", "hostPath": "/var/log/Container_ID", "mode": "RW" }

      I am new to it, I have seen people asking the same question, but no solution is mentioned. so can someone help on this?

      I tried it as below, but it created a file or folder called $MESOS_TASK_ID in /var/log/. Can you please give more details on this? I am new to DCOS and Marathon so please help.

      "volumes": [

      { "containerPath": "/var/log", "hostPath": "/var/log/$MESOS_TASK_ID", "mode": "RW" }

      How this can be done in Marathon JSON?
      I need this dynamic folders in Agent file system to avoid filename conflict between different containers

      Reference : MGI-5232

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_arunkabraham arunkabraham (Inactive)
              Team:
              Orchestration Team
              Watchers:
              Matthias Eichstedt
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: