Problem with docker compose V2 support.

[malylemireflo]

Seems docker-compose command should be updated to docker compose in V2.
https://docs.docker.com/compose/migrate/
Base command should check for .AssumeComposeVersion(ComposeVersion.V2) and remove the hyphen.
I get some errors with the newest docker compose and the command with hypen.
See https://askubuntu.com/questions/1508129/docker-compose-giving-containerconfig-errors-after-update-today

[rsaugier]

Hello. I also get errors when using "docker-compose". More precisely this python error: KeyError: 'ContainerConfig' .
It seems like we're not the only ones and some people on the net seem to have solved this error by using docker compose instead of docker-compose.
I suppose on some systems (say Windows with Docker Desktop) docker-compose can be an alias to docker compose (ie V2). But on others (say in my case a Linux build agent in a popular commercial continuous integration service), it is possible that docker-compose points to V1 and docker compose is the only way to go to have V2.
So yes, fixing FluentDocker by using docker compose instead of docker-compose is probably the right thing to do.
I could try to take a look if nobody handles this, but not immediately.

[mariotoffia]

Hi @rsaugier and @malylemireflo I need to take care of this. Put it on my TODO list and will fix it during my vacation this summer.

Cheers,
Mario