Unable to connect to MariaDb

[Flying--Dutchman]

Component

server

Describe the bug

Using the configuration from the docs, I'm unable to start woodpecker, using MariaDB.

Other containers on the same network can reach the database container without problems.

System Info

devops_woodpecker_ci:
    image: woodpeckerci/woodpecker-server:${WOODPECKER_TAG}
    restart: unless-stopped
    ports:
      - ${WOODPECKER_PORT}:8000
      - 9000
    networks:
      - devops_network
    environment:
      - WOODPECKER_DATABASE_DRIVER=mysql
      - WOODPECKER_DATABASE_DATASOURCE=DBUSER:DBPASSWORD@tcp(DBHOST:3306)/DATABASE?parseTime=true
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=${WOODPECKER_URL}
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=${GITEA_URL}
      - WOODPECKER_SECRET=${WOODPECKER_SECRET}
    depends_on:
      - devops_woodpecker_db

Additional context

Logs:
time="2021-10-10T10:59:20Z" level=error msg="unable to open database file: no such file or directory",
time="2021-10-10T10:59:57Z" level=fatal msg="database ping attempts failed"

Validations

• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.

[6543]

@Flying--Dutchman what WOODPECKER_TAG did you use?!!

[6543]

@Flying--Dutchman you comment on the wrong issue :laughing: but I think I can asume v0.14.1 is the revered version here too

ok that's easy to solve ... we are in transition from v0.14.x to v0.15.0 with breaking changes: https://woodpecker-ci.github.io/docs/migrations#0150

[6543]

• WOODPECKER_DATABASE_DRIVER -> DATABASE_DRIVER
• WOODPECKER_DATABASE_DATASOURCE -> DATABASE_CONFIG

or switch image to "latest"

[Flying--Dutchman]

@Flying--Dutchman you comment on the wrong issue laughing but I think I can asume v0.14.1 is the revered version here too

Note to myself, never answer on a issue during commute, returning from Oktoberfest :sweat_smile:

ok that's easy to solve ... we are in transition from v0.14.x to v0.15.0 with breaking changes:

Ah thank you very much, will change my setup accordingly. Looking forward for v0.15.