Dockest does not work with docker-compose V2

[oscarlgz]

Describe the bug

docker-compose V2 config command omits version from output. dockest cannot run as when validating compose file(s) it expects version to be present.

See this issue for reference.

I'm not sure what would be the best way to remedy this. Possibly just remove the version check in this line.

[erikengervall]

Indeed, ran into this myself recently. I'll give it some though - might release a temporary patch just to get things working again while working on a proper solution.

[oscarlgz]

That would be nice 👍

[erikengervall]

@oscarlgz give v3.0.1 a try when you've got a chance

works pretty well on my end

[oscarlgz]

Works here! Thanks 🎉

[celiolatorraca]

Hey!

Bumping to version 3.0.1 solved the version issue, but now it seems that docker-compose reads the published ports as string and dockest expects it to be integer

Are you having this issue?

v1 output:

postgres:
    environment:
      POSTGRES_DB: ...
      POSTGRES_PASSWORD: ...
      POSTGRES_USER: ...
    image: ...
    ports:
    - published: 5434
      target: 5432

v2 output:

postgres:
    environment:
      POSTGRES_DB: ...
      POSTGRES_PASSWORD: ...
      POSTGRES_USER: ...
    image: ...
    networks:
      default: null
    ports:
    - target: 5432
      published: "5434"

[celiolatorraca]

We tried in 2 different version os docker-compose.

On version 2.2.3 the published port comes as an integer,
But on version 2.3.3 it comes as a string

Should we maybe accept both integer and string?

[erikengervall]

We tried in 2 different version os docker-compose.

On version 2.2.3 the published port comes as an integer, But on version 2.3.3 it comes as a string

Should we maybe accept both integer and string?

Sounds like a good idea 👍

Will create a new issue referencing this one.