Add Support for docker-compose 3.4

[kitingChris]

$ kompose convert -f docker-compose.yml 
FATA Version 3.4 of Docker Compose is not supported. Please use version 1, 2 or 3

Is support for 3.4 already in sight?

[PureKrome]

Same here for version 3.5 :( sadness

[hangyan]

It should not be. I have check the latest code , we have support 3.4/3.5 now. Which versions of kompose you guys use?

[PureKrome]

just downloaded the latest a version, now.

PS C:\> c:\temp\kompose version
1.17.0 (a74acad)
PS C:\>

EDIT:

I got this version because I clicked the link on Kompose.io website:

[hangyan]

@PureKrome Sorry about that, i think the support is only is the master branch and not release yet..

[PureKrome]

yep. confirmed @hangyan

PS C:\> c:\temp\kompose version
1.18.0 (06a2e56)
PS C:\projects\personal\hornet\Hornet.Backend> C:\temp\kompose.exe convert -f .\docker-compose.yml
�[31mFATA�[0m Version 3.5 of Docker Compose is not supported. Please use version 1, 2 or 3
PS C:\projects\personal\hornet\Hornet.Backend>

EDIT: for others reading this ... as of version 1.17.0 it supposedly supports 3.3 and under....

[PureKrome]

@hangyan so has this been released/working yet? what version is this / will this be in?

[hangyan]

Well i'm not in charge of the release, but usually there will be a monthly release. It's merged in master already, you can check it out

[Quinncuatro]

Are there directions on how to download the source, build, and use the latest versions while we're waiting for an "official" release of v1.18?

[PureKrome]

and also .. can we get a release soon?

99% of people don't want to / can't / or know how to (as @Quinncuatro has said, above) build latest.

[Quinncuatro]

Yeah. I don't want to sound like an ungrateful asshole, because this seems really cool.

But this should be keeping better pace with docker-compose's release cadence, especially considering it's owned by the K8s GitHub org.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.