Open jasalt opened 1 week ago
Testing with latest podman-static binary installed from repo and podman-compose (from pipx):
$ podman-compose -v
podman-compose version 1.2.0
podman version 5.3.0
Running Bitnami WordPress and MariaDB images individually with podman
works (as documented):
podman network create wordpress-network
podman volume create mariadb_data
podman run --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_wordpress \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_wordpress \
--network wordpress-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
podman volume create wordpress_data
podman run --name wordpress \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env WORDPRESS_DATABASE_USER=bn_wordpress \
--env WORDPRESS_DATABASE_PASSWORD=bitnami \
--env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
--network wordpress-network \
--volume wordpress_data:/bitnami/wordpress \
bitnami/wordpress-nginx:latest
Some issue with podman-compose
with network discovery apparently not working.
Works with Podman Desktop on Mac, so maybe there is some issue with podman-static and podman-compose not playing nice together on Debian 12.
Worked with more clean setup with podman-static 4.9.4 on one Debian 12 VPS, so might be because of some local config issue in part at least.
Hangs after
mariadb
is up butwordpress
container fails to connect: