Skip to main content

Problems connecting and working with the database when using docker

I am trying to run my project using PHP-FPM, PHP-CLI. Through CLI I can create or delete schemas from the database, or load fixtures

github docker file https://github.com/SyntaxErrorLineNULL/start-mobile/tree/main/docker

docker-compose file

version: '3.8'

services:
    nginx:
        container_name: mobile_nginx_dev
        image: nginx
        volumes:
            - ./docker/nginx/:/etc/nginx/conf.d
            - ./:/app
        links:
            - php-fpm
        ports:
            - '8000:80'

    php-fpm:
        container_name: mobile_php-fpm
        build:
            context: docker
            dockerfile: php-fpm/Dockerfile
        environment:
            DB_HOST: api-postgres
            DB_USER: app
            DB_PASSWORD: secret
            DB_NAME: app
        ports:
            - 8080:8080
        volumes:
            - ./:/app
        working_dir: /app
        links:
            -   start-mobile-database

    php-cli:
        container_name: mobile_php-cli
        build:
            context: docker
            dockerfile: php-cli/Dockerfile
        environment:
            DB_HOST: api-postgres
            DB_USER: app
            DB_PASSWORD: secret
            DB_NAME: app
        volumes:
            - ./:/app
        links:
            - start-mobile-database

    start-mobile-database:
        image: mysql:8.0
        ports:
            - "3306:3306"
        command: --default-authentication-plugin=mysql_native_password
        environment:
            MYSQL_DATABASE: app
            MYSQL_USER: app
            MYSQL_PASSWORD: secret
            MYSQL_ROOT_PASSWORD: root
        volumes:
            - ./dump:/docker-entrypoint-initdb.d
            - ./conf:/etc/mysql/conf.d
            - persistent:/var/lib/mysql
        networks:
            - default
volumes:
    persistent:

Makefile

init: down build up api-composer-install init-db
up:
    docker-compose -f docker-compose.yaml up -d
down:
    docker-compose -f docker-compose.yaml down -v --remove-orphans
build:
    docker-compose -f docker-compose.yaml build --pull
api-composer-install:
    docker-compose -f docker-compose.yaml run --rm php-cli composer install
api-composer-update:
    docker-compose -f docker-compose.yaml run --rm php-cli composer update
init-db:
    docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:schema:drop --force && \
   docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:schema:create
clear-cache:
    docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:cache:clear-metadata && \
    docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:cache:clear-query
load-fixture:
    docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:fixtures:load

env file

DATABASE_URL="mysql://app:secret@start-mobile-database/app"

Problem When I try to lift the container, I get the error

.........
docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:schema:drop --force && \
   docker-compose -f docker-compose.yaml run --rm php-cli bin/console doctrine:schema:create
Creating start-mobile_php-cli_run ... done

In ExceptionConverter.php line 103:
                                                                                  
  An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused  
                                                                                  

In Exception.php line 26:
                                             
  SQLSTATE[HY000] [2002] Connection refused  
                                             

In Driver.php line 28:
                                             
  SQLSTATE[HY000] [2002] Connection refused  
                                             

doctrine:schema:drop [--em EM] [--dump-sql] [-f|--force] [--full-database]

ERROR: 255
make: *** [Makefile:20: init-db]

I will answer some things in advance:

  1. Before adding PHP-FPM and CLI, there was a container with the same database, and there were no problems in the work, all commands for working with Doctrine were successful.
  2. I can connect from the side to the database and work with it.
  3. The config of the env file has not changed, and remained from the old container:
version: '3.8'
services:
  db:
    image: mysql:8.0
    ports:
      - "3306:3306"
    command: --default-authentication-plugin=mysql_native_password
    environment:
      MYSQL_DATABASE: app
      MYSQL_USER: app
      MYSQL_PASSWORD: secret
      MYSQL_ROOT_PASSWORD: root
    volumes:
      - ./dump:/docker-entrypoint-initdb.d
      - ./conf:/etc/mysql/conf.d
      - persistent:/var/lib/mysql
    networks:
      - default
volumes:
  persistent:

What's my mistake? Thanks in advance for your reply!



source https://stackoverflow.com/questions/70414152/problems-connecting-and-working-with-the-database-when-using-docker

Comments

Popular posts from this blog

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...

Confusion between commands.Bot and discord.Client | Which one should I use?

Whenever you look at YouTube tutorials or code from this website there is a real variation. Some developers use client = discord.Client(intents=intents) while the others use bot = commands.Bot(command_prefix="something", intents=intents) . Now I know slightly about the difference but I get errors from different places from my code when I use either of them and its confusing. Especially since there has a few changes over the years in discord.py it is hard to find the real difference. I tried sticking to discord.Client then I found that there are more features in commands.Bot . Then I found errors when using commands.Bot . An example of this is: When I try to use commands.Bot client = commands.Bot(command_prefix=">",intents=intents) async def load(): for filename in os.listdir("./Cogs"): if filename.endswith(".py"): client.load_extension(f"Cogs.{filename[:-3]}") The above doesnt giveany response from my Cogs ...