-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pod creation disabled by default #673
Comments
The last stable 1.0.3 and current stable 1.0.6 have same behavior which is no pod by default The next stable would have pod creation enabled by default. I believe pod creation is good default. Any suggestion? |
The reason of confusion that many people were using the devel branch because we took too much time to release new stable. |
Ah I see, thanks! Yes, we - as many others - have been using the devel branch because the stable 1.0.3 release wasn't working for us. I would definitely vote for pod creation by default. |
I don't understand this... I've been reading though the issues and there are suggested solutions that are not working (anymore?). For example this is not working (for me):
I'm new to podman and podman-compose and want that my compose file creates a pod. Nothing I've found helped me so far. Running on stable, installed through dnf install.
Sorry if this is the wrong place, but I did not want to open another issue, with the same problem. |
we have just released a newer stable version 1.0.6, please update to that version
you can use in the latest stable version
|
that does the trick. Thank you. When running When recreating the pod while all containers are running, works as expected! |
|
@mawe42 thanks for opening an issue. |
Since commit f6dbce3, podman-compose has switched the default behaviour for creating a pod. Before this change, there was a
--no-pod
option with defaultFalse
. Now there is a--in-pod
option with defaultFalse
.If this change was intentional, then it might be good to advertise / document it somewhere IMHO. But I would think having
--in-pod
default toTrue
to keep backwards compatible would be very good for existing users (including me...)The text was updated successfully, but these errors were encountered: