-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow published binding port to be string #313
base: master
Are you sure you want to change the base?
Allow published binding port to be string #313
Conversation
…iour after version 2.3.3
✅ Deploy Preview for dockest canceled.
|
@erikengervall Should we convert the string ports to number when validating? I noticed that we expect the ports to be number in a few places afterwards... |
Good question... Kinda want to roll forward and make a note that one has to upgrade docker compose if they wish to use the upcoming version, rather than making it backwards compatible WDYT? |
Well! Sounds also good The only problem is that we may still need to parse the string to integer at some point. If we choose the "roll forward" approach, we would need just to bump a major version and make it clear somehow that the new version requires docker compose 2.3.x and the older versions should be used if version is lower than that |
Hello guys, |
I'm fine with a major bump with this restriction 🙂
@emrahyldrm apologies, haven't had the time to sit down and flesh out the code for the above suggestions. I'd be happy to review a PR containing upgrades to docker compose 2.3.x and do a major bump! |
Has there been an official response from the docker team to confirm what the desired behaviour should be? According to their example in their own docs about specifying ports, the value is a number (even though the If it is a bug on their end, would I wrote a small proof of concept (before I saw this thread, oops!) that normalizes the |
Since docker compose version 2.3.x, the default behavior now is to return the published binding port as string, which breaks the dockest validation.
This PR fixes the issue #300
docker/compose#9306