-
Notifications
You must be signed in to change notification settings - Fork 489
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
Compatibility spreadsheet #26
Comments
thank you, this project was started as a simple script that can do two commands it was just yesterday when I added proper argument parsing and proper system for sub-commands. I hope during this week (Eid Al-Adha Vacation) I will be able do all of those commands properly with proper options. |
|
NP, thanks for your work! You stepped in when the Podman people decided to ignore simpler use cases. It should be an official project. I forgot to add the options for Feedback: if you're going to take the project a little more seriously maybe the .MD's could be improved?
And if you need help with something maybe list everything in an issue and pin it? I can't code but maybe I could help in other ways. |
valid point
valid point, but now now, maybe after v1.0. because in that case people will stick to the stable branch and I won't be able to catch a simple typo like this one. v1.0 is not taking to long, maybe a week from now.
end-user should not care about those (leave it to default will just work). those are workarounds started initially because it was impossible to implement unfortunately, this will remain until user-space networking is enhanced (currently we can't run two containers with same ports, ex. a redis and its replica using same port) thank you for your feedback, keep it coming. |
Having the options is great, being explicit is always better. I was just nitpicking about their names (e.g. 1podfw) being a little weird, but it's not important!
Maybe having a Shortcomings-like page for Podman Compose. Like what problems are currently present, what can't be fixed because of incompatibilities or lack or daemon. Or they could be listed in a column if you decide to use the "compatibility table". |
It means create one pod and do port forwarding in the pod not in containers. Please read mapping section in readme and feel free to suggest better names. |
Is it ready for production? Must we use development branch? |
I've created that branch because I've made drastic changes to how we parse sub-commands arguments, and made the default is attach not detach. within a single week, I hope we can iron all issues and merge it again. |
Looks like env-file is missing from run. |
Of course it would be better to have a proper compatibility page (containers#26)
Of course it would be better to have a proper compatibility page (#26)
I've noticed https://github.com/muayyad-alsadi/podman-compose/blob/master/CONTRIBUTING.md#missing-commands-help-needed is incomplete.
So I parsed docker-compose commands and added to this spreadsheet https://file.io/1Gx0gD (alternative link: https://filebin.net/258jxepc4lefjmst/podman-compose.ods?t=mlsgj9yu)
Markdown tables are messy so it's an ods file. I'm sure it's easy to convert either with some online service or just export to csv and do a quick replacement.
ps: you don't need to credit me or anything, I'm just trying to help but I'm not much of a programmer
The text was updated successfully, but these errors were encountered: