Defaulting to --pod on breaks compose file with --userns

[deliciouslytyped]

7f5ce26 breaks one of my compose files because Error: --userns and --pod cannot be set together. Passing --in-pod=False or something, would presumably fix this, but

Is there a way to disable --pod in the yaml? If not, can there be a way added to do it from here on out, or can this somehow be fixed?

I tried looking at the source but couldn't figure out if there is an existing way to do it.

[MrSSvard]

I think the check needs to be updated too. The only way to have it not be in a pod that I figured out is --in-pod ""
This worked before when the default was False as any "--in-pod" argument meant you wanted a pod.

A completely new argument probably needs to be created unless we either revert the default or occupy a special pod name "False" that means no pod will be used.

[uosis]

podman compose --in-pod= up works, but this change of behavior is not great. Why is it desirable to default to running in pod? It seems like a needless deviation from docker compose behavior.

[camporter]

Same issue here, strange that the default behavior is to break userns options, which is incredibly necessary when dealing with a mix of rootful and rootless containers under podman.

[schugabe]

Same issue here that change and breaks pretty much all my projects.

[mokibit]

@deliciouslytyped thanks for opening an issue.
The issue was fixed in #964 by adding a custom section in the compose file so the user can set the preferred value for --in-pod.
@schugabe, @camporter this PR should also fix your errors (set --in-pod to False in your compose file when you want to use --userns).
@p12tic the problem can be closed.