Error to parse docker-compose v3 format

[pivulic]

Problem

When trying to create named volumes that can be reused across multiple services (without relying on volumes_from due to "PersistentVolumeClaim is not bound"), kompose is unable to parse docker-compose.yml version 3 format.

See: https://docs.docker.com/compose/compose-file/#/volume-configuration-reference

How To Recreate

1. Create file:touch docker-compose.yml

2. Copy/paste:

   version: "3"
   services:
     db:
       image: db
       volumes:
         - data-volume:/var/lib/db
     backup:
       image: backup-service
       volumes:
         - data-volume:/var/lib/backup/data
   
     volumes:
       data-volume:
   

3. Run: kompose up -f docker-compose.yml

Actual Result

ERRO Could not parse config for project test : yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `3` into config.RawService
FATA Failed to load compose file: yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `3` into config.RawService

Expected Result

docker-compose.yml should successfully be converted and deployed.

[procrypt]

@pivulic Kompose does not support docker-compose version 3 yet.

[michaelharrer]

when will it be available? (roundabout)

[cdrage]

@surajssd Hey man, do you know if this will be updated upstream in libcompose?

[cdrage]

Ahhhh, just found the issue: docker/libcompose#421

We'll have to wait for this to be updated upstream @michaelharrer @pivulic

[surajssd]

yeah v3 is still WIP in upstream and I guess once that is done we can move to it.

[cdrage]

@michaelharrer @pivulic

The best way to "workaround" this is simply removing the "deploy" section of your V3 file and changing the v3 value to v2 and it'll work fine. Luckily there aren't any too major changes between the versions :)

[pivulic]

What "deploy" section? :) The reason why I'm trying the v2 version, is to be able to use named volumes, instead of using volumes_from, trying to get around the "PersistentVolumeClaim is not bound") issue.
But I'm going to try and create the Persistent Volume in my cluster before running kompose up (using a v2 docker-compose.yml), as you recommend in #411 (comment) :)

[cdrage]

@pivulic Ahhhhh. I got my facts wrong. I thought the only large difference was the deploy section of v3. They added named volumes too! We'll see what we can do to fix it. Funny enough, another issue was just opened in regards to using underscores and such in volume names (bug), we could possibly fix two issues with one PR :)

[cdrage]

I'm labeling this as a bug with libcompose as this will need to be supported upstream as well as downstream within Kompose.

[surajnarwade]

@surajssd @kadel , can you please add compose v3 label here ?

[cdrage]

@surajnarwade done

[cdrage]

@pivulic #600 has now been merged! 🎉 🎉 🎉

[pivulic]

Wohoo!