Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error when configuring the mysql database

Open
#390 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, mariadb, shell
Domain
databases, devops

Research direction

Start with the container startup path that logs “Configuring the MySQL database” and reproduce the failure against MariaDB 11.2.2 using the supplied environment settings. Compare the SQL reported at line 1 with the MariaDB version in use; done means the image starts successfully and the database is configured without the syntax error.

Written by the indexing model from the issue text.

Description

Awaiting response

I downloaded image version 2.6.7
When I run the container, wallabag does not start up and the following error is in the log file:

Starting wallabag ... Waiting for database ... Configuring the MySQL database ... ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci' at line 1

I'm using MariaDB 11.2.2 as the database

My wallabag.env:

SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
SYMFONY__ENV__DATABASE_HOST=mariadb
SYMFONY__ENV__DATABASE_PORT=3306
SYMFONY__ENV__DATABASE_USER=***
SYMFONY__ENV__DATABASE_PASSWORD=***
SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
SYMFONY__ENV__DOMAIN_NAME=***
SYMFONY__ENV__MAILER_HOST=***
SYMFONY__ENV__MAILER_USER=***
SYMFONY__ENV__MAILER_PASSWORD=***
SYMFONY__ENV__FROM_EMAIL=***

Dominant language
Shell
Stars
771
Forks
168
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wallabag/docker

All issues in wallabag/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.