Uploaded image for project: 'Coopr'
  1. Coopr
  2. COOPR-806

Docker port management should use actual mapped ports

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 0.9.10 Code Name: Mensa
    • Component/s: plugins
    • Labels:
      None
    • Rank:
      1|hzze73:

      Description

      The current implementation of port mapping in the DockerAutomator assumes a 1:1 mapping, and doesn't allow for using ranges, as Docker does. With Docker, I can give a port range to map to a given container port, and Docker will assign the first available out of the list.

      docker run -d -p 3300-3309:3306 mysql
      

      Our current port conflict detection code will treat this range as a single port and will fail the task, erroneously.

        Attachments

          Activity

            People

            • Assignee:
              mattwuenschel Matt Wuenschel
              Reporter:
              chris Chris Gianelloni
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: