jasalt / phel-wp-plugin

WordPress plugin skeleton and general resources about using Phel (Lisp) within WordPress.
GNU General Public License v2.0
2 stars 1 forks source link

Not starting with `podman-compose up` using podman-static on Debian #1

Open jasalt opened 1 week ago

jasalt commented 1 week ago

Hangs after mariadb is up but wordpress container fails to connect:

podman-compose up
...
...
...
[mariadb]   | 2024-11-16 17:22:16 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
[mariadb]   | Version: '11.4.4-MariaDB'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
wordpress 17:23:13.21 ERROR ==> Could not connect to the database
exit code: 1
jasalt commented 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.

jasalt commented 1 week ago

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.

jasalt commented 1 week ago

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.