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

Remote URLs in uris section cause issues with executing the command

    Details

    • Type: Task
    • Status: Resolved
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Using this file works:

      {
        "id": "ups1.0.0",
        "cmd": "mv aerogear-unifiedpush-server-1.0.0.Final/databases/unifiedpush-h2-ds.xml wildfly-8.1.0.Final/standalone/deployments && mv aerogear-unifiedpush-server-1.0.0.Final/servers/unifiedpush-auth-server.war wildfly-8.1.0.Final/standalone/deployments && mv aerogear-unifiedpush-server-1.0.0.Final/servers/unifiedpush-server-wildfly.war wildfly-8.1.0.Final/standalone/deployments && cd wildfly-8.1.0.Final && sed \"s/8080/$PORT/g\" < ./standalone/configuration/standalone.xml > ./standalone/configuration/standalone-mesos.xml && ./bin/standalone.sh -b 0.0.0.0 -c standalone-mesos.xml",
        "mem": 1024,
        "cpus": 1.0,
        "instances": 1,
        "uris": [
          "file:///Users/matzew/Mesos_Downloads/wildfly-8.1.0.Final.tar.gz",
          "file:///Users/matzew/Mesos_Downloads/aerogear-unifiedpush-server-1.0.0.Final-dist.tar.gz"
        ]
      }
      

      before submitting the JSON file to Marathon, I did download the files from:

      • "http://download.jboss.org/wildfly/8.1.0.Final/wildfly-8.1.0.Final.tar.gz",
      • "https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/1.0.0.Final/aerogear-unifiedpush-server-1.0.0.Final-dist.tar.gz"

      Once downloaded, submitting the above works and the server is launched.

      However, I am not sure why this does not work, when I use the above 'remote' URLs inside of the uris section instead of the file:/// local URIs

      Is this a bug on Marathon?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_matzew Matthias Wessendorf (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: