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

Convert version 3.5 of Docker Compose is not supported #1058

Open
jvitor83 opened this Issue Aug 1, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@jvitor83
Contributor

jvitor83 commented Aug 1, 2018

I have the following docker-compose.yml:

version: "3.5"

services:

  helloworld:
    image: tutum/hello-world
    ports:
      - 80:80
    networks:
      - helloworld-network

networks:
  helloworld-network:
    name: helloworld-network

Executing docker-compose up i can up my service using the network name feature introduced at version 3.5

With that feature, i can use multiples docker-compose.yml and allow them to connect to each other using a specific network name

My idea is to use kompose convert -f docker-compose.yml and allow to generate the k8s ignoring the networks as it already does (not supported - and it is what i expect).
But instead, it is given the following error: Version 3.5 of Docker Compose is not supported. Please use version 1, 2 or 3

I guess it is time to update to allow a greater version of compose spec.

FYI: Even changing the version at docker-compose.yml to 3, the error kompose convert gives is: Additional property name is not allowed. But allowing use as version 3 is not a solution since docker-compose up doesn't work unless is 3.5.

@hangyan

This comment has been minimized.

Member

hangyan commented Aug 1, 2018

@jvitor83 We not still working on support the miner versions of compose. After the full research about what added in version 3.4 and 3.5, we will add support for 3.5

@Doqnach

This comment has been minimized.

Doqnach commented Oct 11, 2018

any ETA on this? would love to convert a 3.5+ compose file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment