From 7d77a1a0563c465882c39670e496ecbd8e2e6ba1 Mon Sep 17 00:00:00 2001
From: uprightbass360 <uprightbass360@gmail.com>
Date: Sat, 11 Oct 2025 14:13:20 -0400
Subject: [PATCH] Remove unsupported pull_policy directives for podman
 compatibility

Docker Compose v3 pull_policy is not supported by podman-compose.
This causes warnings and potential issues during container deployment.

Removed pull_policy from:
- ac-mysql service
- ac-backup service
- ac-db-init service
- ac-db-import service

This improves compatibility with podman while maintaining full Docker support.
---
 docker-compose-azerothcore-database.yml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docker-compose-azerothcore-database.yml b/docker-compose-azerothcore-database.yml
index e3463f7..a91a647 100644
--- a/docker-compose-azerothcore-database.yml
+++ b/docker-compose-azerothcore-database.yml
@@ -6,7 +6,6 @@ services:
   # Step 1: MySQL database
   ac-mysql:
     image: ${MYSQL_IMAGE}
-    pull_policy: ${IMAGE_PULL_POLICY}
     container_name: ${CONTAINER_MYSQL}
     environment:
       MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
@@ -50,7 +49,6 @@ services:
   # Step 2: Backup service
   ac-backup:
     image: ${MYSQL_IMAGE}
-    pull_policy: ${IMAGE_PULL_POLICY}
     container_name: ${CONTAINER_BACKUP}
     environment:
       MYSQL_HOST: ${CONTAINER_MYSQL}
@@ -86,7 +84,6 @@ services:
   # Step 3: Database initialization (one-time setup)
   ac-db-init:
     image: ${MYSQL_IMAGE}
-    pull_policy: ${IMAGE_PULL_POLICY}
     container_name: ${CONTAINER_DB_INIT}
     volumes:
       - ${STORAGE_PATH}/mysql-data:/var/lib/mysql-persistent
@@ -121,7 +118,6 @@ services:
   # Step 4: Database import (one-time setup - run after db-init)
   ac-db-import:
     image: ${AC_DB_IMPORT_IMAGE}
-    pull_policy: ${IMAGE_PULL_POLICY}
     container_name: ${CONTAINER_DB_IMPORT}
     user: "0:0"
     networks: