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
Add support for podman compose #139
Add support for podman compose #139
Conversation
@lcarva Is this still a draft? Or is it ready for review? |
I think the one thing I'd like to do is create a little |
This is ready for review and no longer in draft state. |
podman rootless cannot access the file directly due to selinux Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
ActiveMQ and RabbitMQ both use the port 5762. Even though the port is not exposed on both containers, podman-compose's use of a pod requires the ports to be unique across all containers within the pod. Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
Fixed the travis issue by rebasing on master and picking up the safety fix. |
This is rough draft of what it takes to run IIB with podman.
I managed to make this work on fedora 31 by using my fork of podman-compose on the branch super-duper, https://github.com/lcarva/podman-compose/tree/super-duper. This fork has a few different things that improve the experience drastically (PRs have been created for each commit):
down -v
so volumes are removed.But more importantly, it's based on the devel branch of podman-compose which contains a lot of fixes not found in the rpm distribution.
The changes in this PR are the bare minimum to work with podman-compose. Each commit, hopefully, explain why the change is needed.
If this is something we want to pursue further, we can probably create a
Makefile
to handle the copy of the system ca bundle while starting up the docker/podman-compose.