[rancher-compose] Support for docker-compose v2 syntax?

[crunchtime-ali]

Is there a timeline on when the docker-compose v2 file format will be supported?

Rancher Compose Version: 0.7.2
Docker Version: 1.10.3
OS: OS X 10.11.4 Beta

Steps to Reproduce:

docker-compose.yml

version: '2'
services:
  web:
    build: .
    ports:
     - "5000:5000"
    volumes:
     - .:/code
  redis:
    image: redis

then execute:

rancher-compose -p NewApp up

Results:

ERRO[0000] Could not parse config for project newapp : yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `2` into project.RawService
FATA[0000] Failed to read project: yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `2` into project.RawService

Expected:

[deniseschannon]

Rancher-compose is based on libcompose and libcompose doesn't support it yet.

docker/libcompose#147

[fuhbar]

@deniseschannon: Apart from the dependency between CLI tool rancher-compose and docker-compose, to which extent are changes necessary to the core (cattle) and ui? Have you already planned these migrational efforts? Just interested to know when version v2 syntax will make it into an official rancher release.

Would be nice to see rancher-compose and docker-compose converge even more. :)

[deniseschannon]

@fuhbar We'll also need to add in any new parameters into cattle as part of the API as well as when we export docker-compose.yml files for stacks. And yes, there will be obvious UI changes needed to show these new parameters. We do plan on making v2 syntax support in a release in the future.

We have added this issue for cattle tracking to at least start tracking some of the missing fields. I still have to do a full comparison of V1 vs V2 syntax and what else might be missing.

#4708

[pascalandy]

+1, compose v2 is how my stack runs at the moment.

[django23]

+1

[pwFoo]

Following here.
Need --tmpfs (docker/compose#2778) and --group-add (docker/compose#3328) support with.

[composer22]

libcompose is experimental as such Rancher-Compose should be considered experimental by association. Use in production at your own risk.

[bradjones1]

Looks like this is primarily blocked by libcompose but they are nearing completion on the ticket referenced above.

[cabrinoob]

+1 for this feature. Any release date? I'am using rancher v1.1.0-dev5 and it always seems not to manage v2 syntax of docker-compose.

[deniseschannon]

@cabrinoob Anything with a milestone is typically in our roadmap. When we add in this feature, we'll also announce it in our release-notes.

[cabrinoob]

OK, sorry^^

[ghost]

+1

[crunchtime-ali]

@deniseschannon: Off-topic: Is there an easy way to view that roadmap? GitHub only shows a single milestone AFAIK.

[deniseschannon]

@dj-hedgehog We now have project planning pages.

https://github.com/rancher/rancher/wiki/Rancher-1.2.0

[roynasser]

I realize this has a milestone of 1.2.0 (so I guess around october?), however it also says "resolved" in status label... Is it implemented in any version?

We are using buildargs quite extensively in order to re-use a bunch of images for similar purposes... compose v2 would allow us to go back to using rancher...

[soumyalj]

Tested the v1.2.0-pre2-rc1. Ran all the rancher-compose-commands related test cases with v2 syntax. Did not find any issues.

[roynasser]

Great news... will test pre2-rc1 soon :)

[deniseschannon]

@RVN-BR Please note that we have only tested for services.

We have to introduce volumes and networks.

[roynasser]

Actually I'm using mostly (or only) build arguments from v2... Havent used volumes or networks... I do use regular links and dependes_on, as well as volumes_from (but have maintained a 1-1 relationship so I dont screw up sidekicks...

[deniseschannon]

Added in support for v2 services, but created separate issues for v2 volumes (#5714) and v2 networks (#5715).