v2 beta - embedded mariadb fails to initialise

📑 I have found these related issues/pull requests

none

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

Tried to create a new docker based uptime kuma instance with embedded mariadb, but mariadb cannot initialise properly and goes into start and stop loop.

👟 Reproduction steps

Create a new uptime kuma instance with docker using this docker compose file:

services:
    uptime-kuma:
        image: louislam/uptime-kuma:beta
        container_name: uptime-kuma
        volumes:
          - ./uptime-kuma-data:/app/data
        ports:
          - 3001:3001
        restart: unless-stopped

👀 Expected behavior

Uptime Kuma would finalise the initialisation of the embedded mariadb

😓 Actual Behavior

start and stop loop of mariadb

🐻 Uptime-Kuma Version

2.0.0-beta.0

💻 Operating System and Arch

Debian 12.7 amd64

🌐 Browser

Edge v130

🖥️ Deployment Environment

• Runtime:
• Database:
• Filesystem used to store the database on:
• number of monitors: 0

📝 Relevant log output

Docker compose log output (click to expand)

uptime-kuma  | Welcome to Uptime Kuma
uptime-kuma  | Your Node.js version: 20.18.0
uptime-kuma  | 2024-10-29T20:56:12Z [SERVER] INFO: Env: production
uptime-kuma  | 2024-10-29T20:56:13Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0
uptime-kuma  | 2024-10-29T20:56:13Z [SERVER] INFO: Loading modules
uptime-kuma  | 2024-10-29T20:56:14Z [SERVER] INFO: Creating express and socket.io instance
uptime-kuma  | 2024-10-29T20:56:14Z [SERVER] INFO: Server Type: HTTP
uptime-kuma  | 2024-10-29T20:56:14Z [SERVER] INFO: Data Dir: ./data/
uptime-kuma  | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json'
uptime-kuma  | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: Starting Setup Database on 3001
uptime-kuma  | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: Open http://localhost:3001 in your browser
uptime-kuma  | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: Waiting for user action...
uptime-kuma  | Request /setup-database-info
uptime-kuma  | Request /setup-database-info
uptime-kuma  | Request /setup-database-info
uptime-kuma  | Request /setup-database-info
uptime-kuma  | Request /setup-database-info
uptime-kuma  | Request /setup-database-info
uptime-kuma  | 2024-10-29T20:56:26Z [SETUP-DATABASE] INFO: Database is configured, close the setup-database server and start the main server now.
uptime-kuma  | 2024-10-29T20:56:26Z [SETUP-DATABASE] INFO: The setup-database server is closed
uptime-kuma  | 2024-10-29T20:56:26Z [DB] INFO: Database Type: embedded-mariadb
uptime-kuma  | 2024-10-29T20:56:26Z [MARIADB] INFO: Embedded MariaDB: /app/data/mariadb is not found, create one now.
uptime-kuma  | 2024-10-29T20:56:28Z [MARIADB] INFO: Embedded MariaDB: mysql_install_db done:Installing MariaDB/MySQL system tables in '/app/data/mariadb' ...
uptime-kuma  | OK
uptime-kuma  |
uptime-kuma  | To start mariadbd at boot time you have to copy
uptime-kuma  | support-files/mariadb.service to the right place for your system
uptime-kuma  |
uptime-kuma  |
uptime-kuma  | Two all-privilege accounts were created.
uptime-kuma  | One is root@localhost, it has no password, but you need to
uptime-kuma  | be system 'root' user to connect. Use, for example, sudo mysql
uptime-kuma  | The second is node@localhost, it has no password either, but
uptime-kuma  | you need to be the system 'node' user to connect.
uptime-kuma  | After connecting you can set the password, if you would need to be
uptime-kuma  | able to connect as any of these users with a password and without sudo
uptime-kuma  |
uptime-kuma  | See the MariaDB Knowledgebase at https://mariadb.com/kb
uptime-kuma  |
uptime-kuma  | You can start the MariaDB daemon with:
uptime-kuma  | cd '/usr' ; /usr/bin/mariadb-safe --datadir='/app/data/mariadb'
uptime-kuma  |
uptime-kuma  | You can test the MariaDB daemon with mysql-test-run.pl
uptime-kuma  | cd '/usr/share/mysql/mysql-test' ; perl mariadb-test-run.pl
uptime-kuma  |
uptime-kuma  | Please report any problems at https://mariadb.org/jira
uptime-kuma  |
uptime-kuma  | The latest information about MariaDB is available at https://mariadb.org/.
uptime-kuma  |
uptime-kuma  | Consider joining MariaDB's strong and vibrant community:
uptime-kuma  | https://mariadb.org/get-involved/
uptime-kuma  |
uptime-kuma  |
uptime-kuma  | 2024-10-29T20:56:28Z [MARIADB] INFO: Embedded MariaDB: /app/data/run/mariadb is not found, create one now.
uptime-kuma  | 2024-10-29T20:56:28Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-29T20:56:28Z [MARIADB] INFO: Stopped Embedded MariaDB: 1
uptime-kuma  | 2024-10-29T20:56:28Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
uptime-kuma  | 2024-10-29T20:56:28Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Stopped Embedded MariaDB: 1
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Stopped Embedded MariaDB: 1
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Waiting for Embedded MariaDB to start...
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Stopped Embedded MariaDB: 1
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-29T20:56:29Z [MARIADB] INFO: Waiting for Embedded MariaDB to start...
uptime-kuma  | 2024-10-29T20:56:30Z [MARIADB] INFO: Stopped Embedded MariaDB: 1

[c3p0vsr2d2]

same error on previous 2 or 3 nightlies.
Sorry, was too lazy to report it.

[louislam]

Is it rootless image? If yes:

⚠️ If file permission is not set correctly, Uptime Kuma will run into startup issues. You should set the data directory to node:node (1001:1001) user.

[c3p0vsr2d2]

I am not using rootless, but there was also this recent change to remove USER node from the docker build file.
Will retry with 1001:1001 set.

[c3p0vsr2d2]

2.0.0-beta.0 (not the rootless image) has same issue with embedded mariadb initialization.
data directory set to root permissions
Logs show:

2024-10-29T20:56:43-07:00 [MARIADB] INFO: Stopped Embedded MariaDB: 1
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Starting Embedded MariaDB
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
...

[louislam]

@high3eam @c3p0vsr2d2 I just enabled MariaDB log to console. You could try the nightly2 image.

@louislam I get this log output with nightly2 (non-rootless):

Nightly2 log

uptime-kuma  | Welcome to Uptime Kuma
uptime-kuma  | Your Node.js version: 20.18.0
uptime-kuma  | 2024-10-30T08:53:01Z [SERVER] INFO: Env: production
uptime-kuma  | 2024-10-30T08:53:02Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0-nightly-20241030074209
uptime-kuma  | 2024-10-30T08:53:02Z [SERVER] INFO: Loading modules
uptime-kuma  | 2024-10-30T08:53:03Z [SERVER] INFO: Creating express and socket.io instance
uptime-kuma  | 2024-10-30T08:53:03Z [SERVER] INFO: Server Type: HTTP
uptime-kuma  | 2024-10-30T08:53:03Z [SERVER] INFO: Data Dir: ./data/
uptime-kuma  | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json'
uptime-kuma  | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: Starting Setup Database on 3001
uptime-kuma  | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: Open http://localhost:3001 in your browser
uptime-kuma  | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: Waiting for user action...
uptime-kuma  | Request /setup-database-info
uptime-kuma  | 2024-10-30T08:53:14Z [SETUP-DATABASE] INFO: Database is configured, close the setup-database server and start the main server now.
uptime-kuma  | 2024-10-30T08:53:14Z [SETUP-DATABASE] INFO: The setup-database server is closed
uptime-kuma  | 2024-10-30T08:53:14Z [DB] INFO: Database Type: embedded-mariadb
uptime-kuma  | 2024-10-30T08:53:14Z [MARIADB] INFO: Embedded MariaDB: /app/data/mariadb is not found, create one now.
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: Embedded MariaDB: mysql_install_db done:Installing MariaDB/MySQL system tables in '/app/data/mariadb' ...
uptime-kuma  | OK
uptime-kuma  |
uptime-kuma  | To start mariadbd at boot time you have to copy
uptime-kuma  | support-files/mariadb.service to the right place for your system
uptime-kuma  |
uptime-kuma  |
uptime-kuma  | Two all-privilege accounts were created.
uptime-kuma  | One is root@localhost, it has no password, but you need to
uptime-kuma  | be system 'root' user to connect. Use, for example, sudo mysql
uptime-kuma  | The second is node@localhost, it has no password either, but
uptime-kuma  | you need to be the system 'node' user to connect.
uptime-kuma  | After connecting you can set the password, if you would need to be
uptime-kuma  | able to connect as any of these users with a password and without sudo
uptime-kuma  |
uptime-kuma  | See the MariaDB Knowledgebase at https://mariadb.com/kb
uptime-kuma  |
uptime-kuma  | You can start the MariaDB daemon with:
uptime-kuma  | cd '/usr' ; /usr/bin/mariadb-safe --datadir='/app/data/mariadb'
uptime-kuma  |
uptime-kuma  | You can test the MariaDB daemon with mysql-test-run.pl
uptime-kuma  | cd '/usr/share/mysql/mysql-test' ; perl mariadb-test-run.pl
uptime-kuma  |
uptime-kuma  | Please report any problems at https://mariadb.org/jira
uptime-kuma  |
uptime-kuma  | The latest information about MariaDB is available at https://mariadb.org/.
uptime-kuma  |
uptime-kuma  | Consider joining MariaDB's strong and vibrant community:
uptime-kuma  | https://mariadb.org/get-involved/
uptime-kuma  |
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: Embedded MariaDB: /app/data/run/mariadb is not found, create one now.
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: mariadbd: Can't create file '/app/data/mariadb-error.log' (errno: 13 "Permission denied")
uptime-kuma  | 2024-10-30  8:53:15 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision  as process 86
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: Number of transaction pools: 1
uptime-kuma  | 2024-10-30  8:53:15 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
uptime-kuma  | 2024-10-30  8:53:15 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95
uptime-kuma  | 2024-10-30  8:53:15 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: Completed initialization of buffer pool
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: End of log at LSN=46996
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: 128 rollback segments are active.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: log sequence number 46996; transaction id 14
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] Plugin 'FEEDBACK' is disabled.
uptime-kuma  | 2024-10-30  8:53:15 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] InnoDB: Buffer pool(s) load completed at 241030  8:53:15
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [Note] Server socket created on IP: '127.0.0.1'.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30  8:53:15 0 [ERROR] Can't start server : Bind on unix socket: Permission denied
uptime-kuma  | 2024-10-30  8:53:15 0 [ERROR] Do you already have another server running on socket: /app/data/run/mariadb/mysqld.sock ?
uptime-kuma  | 2024-10-30  8:53:15 0 [ERROR] Aborting
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: Stopped Embedded MariaDB: 1
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: Starting Embedded MariaDB
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: mariadbd: Can't create file '/app/data/mariadb-error.log' (errno: 13 "Permission denied")
uptime-kuma  | 2024-10-30  8:53:16 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision  as process 97
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: Number of transaction pools: 1
uptime-kuma  | 2024-10-30  8:53:16 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
uptime-kuma  | 2024-10-30  8:53:16 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
uptime-kuma  | 2024-10-30  8:53:16 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95
uptime-kuma  | 2024-10-30  8:53:16 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: Completed initialization of buffer pool
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: End of log at LSN=46996
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: 128 rollback segments are active.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
uptime-kuma  | 2024-10-30  8:53:16 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: log sequence number 46996; transaction id 14
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] Plugin 'FEEDBACK' is disabled.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [Note] Server socket created on IP: '127.0.0.1'.
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30  8:53:16 0 [ERROR] Can't start server : Bind on unix socket: Permission denied
uptime-kuma  | 2024-10-30  8:53:16 0 [ERROR] Do you already have another server running on socket: /app/data/run/mariadb/mysqld.sock ?
uptime-kuma  | 2024-10-30  8:53:16 0 [ERROR] Aborting
uptime-kuma  |
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] INFO: Stopped Embedded MariaDB: 1
uptime-kuma  | 2024-10-30T08:53:16Z [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user

[louislam]

[ERROR] Can't start server : Bind on unix socket: Permission denied

That is strange... Have to find a way to 100% reproduce this. I cannot reproduce it on my Linux machine.

[N0Klu3]

I have this same issue, its a fresh install of Bookworm on RPi5, running Portainer.
Compose:

version: '3.3'
services:
  uptime-kuma:
    image: louislam/uptime-kuma:beta
    container_name: uptime-kuma
    volumes:
      - uptime-kuma:/app/data
    ports:
      - "3005:3001"
    restart: unless-stopped

volumes:
  uptime-kuma:

I get the exact same:

[MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
[MARIADB] INFO: Starting Embedded MariaDB
[MARIADB] INFO: Waiting for Embedded MariaDB to start...

This was a fresh install of UK not a migration.
My migration funnily did work just fine on another RPi5 system.

EDIT
Ironically switching to beta-rootless gets it started and working fine with Embedded MariaDB
Did the builds get switched by any chance?
The notes say: Unable to use embedded MariaDB, you will need to use external MariaDB.
But seems to work better than the 'beta' build?

This is using beta-rootless

2024-10-30T22:35:58Z [MARIADB] INFO: Embedded MariaDB: /app/data/run/mariadb is not found, create one now.
2024-10-30T22:35:58Z [MARIADB] INFO: Starting Embedded MariaDB
2024-10-30T22:35:58Z [MARIADB] INFO: Embedded MariaDB is ready for connections
2024-10-30T22:35:59Z [MARIADB] INFO: Embedded MariaDB started
2024-10-30T22:35:59Z [MARIADB] INFO: Creating basic tables for MariaDB
2024-10-30T22:36:00Z [MARIADB] INFO: Created basic tables for MariaDB
2024-10-30T22:36:00Z [SERVER] INFO: Connected to the database
2024-10-30T22:36:00Z [MIGRATION] INFO: Migration server is running on http://localhost:3001
2024-10-30T22:36:00Z [DB] INFO: Migrating Aggregate Table
2024-10-30T22:36:00Z [DB] INFO: Getting list of unique monitors
2024-10-30T22:36:00Z [DB] INFO: Clearing non-important heartbeats
2024-10-30T22:36:00Z [DB] INFO: No data to migrate

@louislam the above might help?

[louislam]

Bookworm on RPi5

@N0Klu3 Thanks for your hints! I just reproduce this issue on my Pi4 too.

[N0Klu3]

Bookworm on RPi5

@N0Klu3 Thanks for your hints! I just reproduce this issue on my Pi4 too.

Can you confirm that beta-rootless should not have Embedded MariaDB working? As it seems to work just fine?
Or maybe I just misunderstood the upgrade notes?

If it does work, why use non-root over root? Seems like if it works, running it as beta-rootless would be the better options no?

[louislam]

Bookworm on RPi5

@N0Klu3 Thanks for your hints! I just reproduce this issue on my Pi4 too.

Can you confirm that beta-rootless should not have Embedded MariaDB working? As it seems to work just fine? Or maybe I just misunderstood the upgrade notes?

If it does work, why use non-root over root? Seems like if it works, running it as beta-rootless would be the better options no?

Since I implemented this feature last year, the migration guide which I prepared recently was wrong. (I just updated) It should work on both the rootless and the root images.

Actually all issues are probably related to the file permissions. I try my best to handle it smoothly for everyone.

beta-rootless should have better security if you don't need Docker monitors via docker.sock.

[N0Klu3]

Since I implemented this feature last year, the migration guide which I prepared recently was wrong. (I just updated) It should work on both the rootless and the root images.

Actually all issues probably the file permissions. I try my best to handle it smoothly for everyone.

beta-rootless should have better security if you don't need Docker monitors via docker.sock.

Perfect thank you!
beta-rootless it is then :)