-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
API v2 and docker-compose compatibility (Question) #7080
Comments
Yes, we will work with people having compose issues, as long as those compose scripts do not use features that Podman does not support like Docker swarm. One area of concern is around Docker networking, which is quite a bit different then Podman networking. One last caveat is that the Podman Core developers have little experience with Compose, so we will probably be asking for easy reproducers of issues with the way we are supporting the Docker API. |
We also feel(hope) that community will be very helpful in this area. |
Thanks Dan! I think the networking issue is the main challenge for running a simple docker-compose config. Perhaps if podman wants to be compatible with docker-compose and be a drop-in replacement for Docker, it needs to somehow mimic the concept of docker networking via its API. |
We can provide networking very similar as root, but our network commands and API are not a perfect match right now due to our use of CNI. I am going to tackle improving this at some point in the next few months. As rootless, we do not have the necessary privileges, so it is not possible to create networks at present. |
A friendly reminder that this issue had no activity for 30 days. |
Can we assume that podman v2.x.x (with new API) will eventually could work with docker-compose?
PS. I know there is a podman-compose project. But, it's not prod ready yet.
Thanks
The text was updated successfully, but these errors were encountered: