-
Notifications
You must be signed in to change notification settings - Fork 191
Support composefile v3 #421
Comments
Compose v3 is pretty different since it's embedded in Docker now. Is the intention to keep Docker Compose as a separate entity as well, or will that be eventually be deprecated? I'm also not sure if it makes sense to add v3 support to libcompose with aanand/compose-file already around. |
It will still be supported by And the intention is to re-use |
You will still be able to use |
+1 |
+1 |
Hi @vdemeester I'm starting to investigate on how to implement v3 of Docker Compose into libcompose. When going through the code, it's hard to tell whats-what as there is a lack of comments. One particular question I have is the Given a clean-slate, would it be better to implement via https://github.com/aanand/compose-file or adding v3 manually (since, like you said, there's not many differences other than |
This is also implemented in https://github.com/docker/cli/blob/master/cli/command/stack/deploy_composefile.go |
@muka That's what we ended up using in https://github.com/kubernetes/kompose since we didn't get any feedback from @vdemeester on Version 3 of Docker Compose in libcompose. Perhaps one-day the efforts put towards |
@cdrage I am curious, have you directly imported the cli as package or ported the code. Can you share any relevant source? Thx |
Hey @muka see: https://github.com/kubernetes/kompose/blob/master/pkg/loader/compose/v3.go We ended up using the |
Would you put a comment on the project |
@andresvia I'm mainly trying to add support for v1/v2 in |
still open after a year :( no hope |
the docker/cli (moby/cli) functionality is not easily resuable in libcompose as it of course renders whole compose files into "types" of the docker handler. This means "import"ing a massive amount of docker/moby code in as libraries into this project, and either converting them into classic libcompose types, or refactoring libcompose to use the docker/moby types. This means lots of work for Service, Network, Volume etc. Basically, the new cli(ish) unmarshaling code produces objects used in the docker/moby project, not objects from libcompose. |
Referencing to rancher: |
More than a year... |
Any word on this? |
I see Kompose is using docker/cli to parse v3 yamls, so probably community gave up with waiting for libcompose. |
@iBobik That's correct! This project has also been deprecated (libcompose) |
Any chance to implement v3? |
@devs-php sounds like the answer is a hard nope, might have to fork it yourself if you want v3+ |
No description provided.
The text was updated successfully, but these errors were encountered: