-
Notifications
You must be signed in to change notification settings - Fork 771
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
Deprecate Docker Compose Version 2.1, 2.2, and 3.3. Only support 1,2,3,4 (future). #725
Comments
ping @kadel @surajnarwade @surajssd @containscafeine for discussion. |
I think we don't support any minor version in kompose as of now, |
I have updated http://kompose.io/conversion/ to outline that we only support major versions. Can we close this? @kadel @surajnarwade @surajssd @containscafeine |
yeah, we can close this |
Sorry to resurrect a closed issue but what syntax for 2/3 is supported? There's quite a bit of difference between 2, 2.1, 2.4, etc. I have a 2.4 compose with healthcheck for example, how do I map that? |
@mterron We support all versions now. If you have troubles, you can always upgrade to version 3 and deploy that. Healthcheck works on there! http://kompose.io/conversion/ |
See:
https://docs.docker.com/compose/compose-file/compose-versioning/#versioning
I propose that we deprecate any minor versions and only support major versions.
Problem case is that version 2.1 and 2.2 isn't support by https://github.com/docker/libcompose and we would have to contribute up-stream.
Docker is pushing for Version 3 and is supported by their http://github.com/docker/cli tool, however, 3.1, 3.2 and 3.3 are moving too quick (3.1 and 3.2 aren't even mentioned on https://docs.docker.com/compose/compose-file/compose-versioning/#version-3 anymore).
I suggest we only support major versions (1,2,3) and eventually 4 (in the farrrr future).
The text was updated successfully, but these errors were encountered: