Muayyad Alsadi

@garethahealy it's supposed to be fixed in the latest 1.x, please upgrade and test.

this is implemented in this pending pull request https://github.com/containers/podman-compose/pull/453 I've not merged it yet.

Yes, I would love to merge it. I just need to review it.

would you please test this with latest devel version ``` pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz ```

I tried to check non-spacing marks using ``` perl -nle 'if (m/\p{Mn}/) {print "got non-spacing mark at line $."}' podman_compose.py ``` and we got nothing, maybe your problem is from...

> I do not expect podman-compose to parse explicitly for invalid characters. In fact, I assume it does not parse at all but uses some yaml parser. we don't do...

> And sorry, should have done this right away, but I re-tested what I pasted and indeed contains the illegal character, so it is a happy testcase. :) I was...

you can use podman with docker-compose like this https://fedoramagazine.org/use-docker-compose-with-podman-to-orchestrate-containers-on-fedora/ but podman-compose have different goals that focus on podman benefits over docker that it can work without daemon and in use...

let me give you an example to see how `podman-compose` and `docker-compose` approach the problem differently let's say you run the `podman` socket rootless ``` export DOCKER_HOST=///run/user/$UID/podman/podman.sock ``` and you...

> so we can't even use their python parser currently I'm not using their python parser, so this change does not impact us in any way > the docker-compose is...