Closed D3vil0p3r closed 11 months ago
I'm encountering the same problem here.. strange
This is not an issue with the redmine
image or the example compose file. It is expected that the redmine
container will fail to stay running until it can access the configured database (since it needs to start with a db:migrate
).
I would guess that you need a plugin when using podman (https://github.com/containers/podman-compose/tree/bce40c2db30fb0ffb9264b5f51535c26f48fe983#podman-compose):
podman dnsname plugin: It is usually found in the
podman-plugins
orpodman-dnsname
distro packages, those packages are not pulled by default and you need to install them. This allows containers to be able to resolve each other if they are on the same CNI network.
I installed on Debian the package containernetworking-plugins
(that seems the only one I see related to podman-dnsname), I rebooted the server but I still get the same error when I restart the container. I'm working as rootless.
UPDATE: upgrading Debian 11 to 12 and installing netavark
, removing the containers, reboot and re-run podman-compose up -d
fixed the issue. So netavark
was the needed package. So, summarizing, the needed packages are:
appstream
slirp4netns
netavark
I'm using podman (4.8.0) on my Debian 11 endpoint and using podman-compose (1.0.6) to implement the redmine compose file described in RedMine official guide in Docker Hub:
For running this in Debian, I need also to install
appstream
andslirp4netns
packages to prevent warning/error messages (so I guess they must be documented on your guide in case of podman usage).When I run
podman-compose up -d
, I get:So, no error. Indeed, if I run
podman ps
, I see the running containers:The problem is: when I try to access to the 8080 port of my host, for example by
curl
, I get "[connection reset](curl: (56) Recv failure: Connection reset by peer)" message. The 8080 TCP port is reachable, I tested it bynmap
.By checking
podman logs athena_db_1
I get no errors:But when I run
podman logs athena_redmine_1
, I get a lot of repeated error messages:So I guess this is the reason the web server inside the container does not start. Why I'm getting this by using podman? By docker it works correctly.