Docker compose: Gitea Mysql timeout

Install/Maintain/Configure
1

Hello,
I am having trouble with a simple setup for Gitea + mysql on my Synology nas.
I had it working fine as individual containers previously but i wanted to use the new “Container Manager”, as it supports “docker compose” and makes the update of container easier.

I spent a day on this and it still fails, hence here i am.

Both containers are up and running.
I can connect and load the setup page for Gitea, but when i press the install button it times out.
All i can see is that somehow gitea container can’t talk to the mysql container… it just times out every time.

The resolved IP:PORT returned in the timeout message matchs the mysql container information and should work.

The mysql container is “/usr/sbin/mysqld: ready for connections”, so i guess it’s happy…

Both containers are on the same network and were created as a “project” with a docker compose yalm file.

Am i missing an obvious step ?

I would be gratefull if any one could test it on their side or tell me who to contact.
Tried Docker discord, told me it looks good, it is likely a Gitea issue.
Contacted Synology, still waiting.
Here i am trying the Gitea side.

Thanks !

Here is the compose.yalm file used:

version: '3.5'

services:
  app:
    image: gitea/gitea:latest
    container_name: gitea-app
    environment:
      - GITEA__database__DB_TYPE=mysql
      - GITEA__database__HOST=db
      - GITEA__database__NAME=gitea
      - GITEA__database__USER=gitea
      - GITEA__database__PASSWD=gitea
    restart: 'unless-stopped'
    volumes:
      - /volume1/docker/projects/gitea/data:/data
    ports:
      - "12022:22"
      - "12080:3000"
    depends_on:
      - db

  db:
    image: mysql:8
    container_name: gitea-mysql
    restart: 'unless-stopped'
    environment:
      - MYSQL_ROOT_PASSWORD=gitea
      - MYSQL_USER=gitea
      - MYSQL_PASSWORD=gitea
      - MYSQL_DATABASE=gitea
    volumes:
      - /volume1/docker/projects/gitea/mysql:/var/lib/mysql
2

I can confirm that it works if i hand create two seperate separate container, without using the Project option (compose), and link them afterwards myself.

So there is an issue with the Project (compose) approach where it configure a single network.
Looks like a Synology docker issue, but can’t say for sure.

3

Try to make them in the same network


networks:
  gitea:
    external: false
services:
  app:
    image: gitea/gitea:latest
    networks:
      - gitea
  db:
    networks:
      - gitea
4

Thanks, I already tried that and had the same result unfortunately.
Actually docker compose will already create a default network for them if none is specified and assign it to the two of them.