ports not accepting a range in yml

[awsmsrc]

the command following command works as of docker 1.5:

docker run -p 3000-3002:3000-3002 port_test

specifying ports this way in the docker-compose.yml always results in a cannot start container exit status 2

[tvcutsem]

Ran into the same issue yesterday. Specifying the port range as a string also doesn't help. Here's the offending section from my yml file:

ports:
  - "50000-50050:50000-50050"

[dougborg]

We have run into this issue as well. We were expecting something like this to "just work":

ports:
  - "1000-1019"

[yuval-k]

#dibs

[awsmsrc]

gonna work on this one at the docker party tonight

[yuval-k]

hi @awsmsrc, I already started working on this, FYI - do you want to help us?

[DXist]

+1

[benbot]

Has this been in any release yet?

[awsmsrc]

yeah would be good to get an update @aanand

[cloetzi]

+1

[aanand]

It's been implemented by @uvgroovy in #1191, but needs rebasing.

[yuval-k]

@aanand rebasing done

[reidrac]

+1

[willbarrett]

Looks like the implementation just needs docs and a rebase. I'm sure we'd all be grateful to @uvgroovy if that happened soon :)

[yuval-k]

Hi,
I just realized that missed the documentation request from the PR... sorry for that - on it right now
thanks @willbarrett

[tpires]

Can someone close this? Looks like this is already merged here.

[jasonm-makerbot]

👍

[brunoborges]

Why only "ports:" supports range? Why not "expose:" too?

Also, is it possible to fix the documentation to go into more detail on the differences between ports and expose? It is still not clear on what happens in each case.

[vpillac]

Hi, my docker-compose files stopped working after updating to docker-compose version 1.5.2 (from MacOS Docker Toolbox 1.9.1).

Service 'xxx' configuration key 'expose' '0' is invalid: should be of the format 'PORT[/PROTOCOL]'

While the file contains

  expose:
  - "8200-8219"

Replacing the range by a single port "resolves" the issue.

[dnephin]

Ah, I guess that is valid. Could you open a new issue about it?

I wonder if that was added recently to expose, I don't remember seeing it in the docs when we implemented it.

[vpillac]

New issue created: #2611