Describe the bug
When starting the piler 1.4.9 Docker container, the startup script fails to connect to MariaDB with the following error, looping indefinitely:
ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not support it
This regression does not occur with piler 1.4.8.
To Reproduce
- Start piler 1.4.9 using the provided
docker-compose.yaml
- Observe the piler container logs
- See the SSL error repeating every 5 seconds in the
wait_until_mysql_server_is_ready loop
Expected behavior
Piler connects to MariaDB without SSL errors, as it did in version 1.4.8.
Root cause
Piler 1.4.9 uses ubuntu:26.04 as its base image (confirmed by php8.5-fpm in start.sh). Ubuntu 26.04 ships a newer mariadb-client-core package where the default SSL mode for TCP connections changed to REQUIRED. The MariaDB server has no SSL certificates configured, so the connection fails.
The create_my_cnf_files() function in docker/start.sh generates /etc/piler/.my.cnf without any SSL option:
printf "[client]\nhost = %s\nuser = %s\npassword = %s\n..."
Piler 1.4.8 used an older Ubuntu base image where the mariadb client did not require SSL by default on TCP connections.
Fix
Add ssl=false to the [client] section in create_my_cnf_files():
printf "[client]\nhost = %s\nuser = %s\npassword = %s\nssl=false\n[mysqldump]\nhost = %s\nuser = %s\npassword = %s\n" \
"$MYSQL_HOSTNAME" "$MYSQL_USER" "$MYSQL_PASSWORD" \
"$MYSQL_HOSTNAME" "$MYSQL_USER" "$MYSQL_PASSWORD" \
> "$PILER_MY_CNF"
This was confirmed by manually adding ssl=false under [client] in the running container — piler connected successfully and completed its initialization.
[client]
ssl=false
host = 127.0.0.1
user = piler
password = piler
[mysqldump]
host = 127.0.0.1
user = piler
password = piler
Piler version:
Additional context
Verified on a NethServer 8 deployment using mariadb:10.11.18. The issue is not specific to the MariaDB server version — it is caused by the newer mariadb client inside the piler container requiring SSL when connecting via TCP to 127.0.0.1.
Describe the bug
When starting the piler 1.4.9 Docker container, the startup script fails to connect to MariaDB with the following error, looping indefinitely:
This regression does not occur with piler 1.4.8.
To Reproduce
docker-compose.yamlwait_until_mysql_server_is_readyloopExpected behavior
Piler connects to MariaDB without SSL errors, as it did in version 1.4.8.
Root cause
Piler 1.4.9 uses
ubuntu:26.04as its base image (confirmed byphp8.5-fpminstart.sh). Ubuntu 26.04 ships a newermariadb-client-corepackage where the default SSL mode for TCP connections changed toREQUIRED. The MariaDB server has no SSL certificates configured, so the connection fails.The
create_my_cnf_files()function indocker/start.shgenerates/etc/piler/.my.cnfwithout any SSL option:Piler 1.4.8 used an older Ubuntu base image where the mariadb client did not require SSL by default on TCP connections.
Fix
Add
ssl=falseto the[client]section increate_my_cnf_files():This was confirmed by manually adding
ssl=falseunder[client]in the running container — piler connected successfully and completed its initialization.Piler version:
piler 1.4.9Additional context
Verified on a NethServer 8 deployment using
mariadb:10.11.18. The issue is not specific to the MariaDB server version — it is caused by the newer mariadb client inside the piler container requiring SSL when connecting via TCP to127.0.0.1.