Alpine Linux 3.21

[crazy-max]

No description provided.

[crazy-max]

Database migration fails since Alpine 3.21 as of now SSL is required with mysql client: https://github.com/librenms/docker/actions/runs/12610894411/job/35145956067?pr=479#step:8:133

Updating database schema...
   INFO  Preparing database.  
  Creating migration table .......................................... 6ms DONE
   INFO  Loading stored database schemas.  
  database/schema/mysql-schema.sql ................................. 13ms FAIL
In Process.php line 270:
  The command "mysql  --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_L  
  OAD_PASSWORD}" --host="${:LARAVEL_LOAD_HOST}" --port="${:LARAVEL_LOAD_PORT}  
  " --database="${:LARAVEL_LOAD_DATABASE}" < "${:LARAVEL_LOAD_PATH}"" failed.  
  Exit Code: 1(General error)                                                  
  Working directory: /opt/librenms                                             
  Output:                                                                      
  ================                                                             
  Error Output:                                                                
  ================                                                             
  mysql: Deprecated program name. It will be removed in a future release, use  
   '/usr/bin/mariadb' instead                                                  
  ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not  
   support it                                                                  
[cont-init.d] 04-svc-main.sh: exited 1.

Last commit of this PR skips SSL by default when checking connection to the database but we can't pass the --skip-ssl during database migration afaik.

There is also this warning:

  mysql: Deprecated program name. It will be removed in a future release, use  
   '/usr/bin/mariadb' instead  

@murrant Is it possible to have an option to set a custom mysql client binary instead of having this hardcoded in librenms? And for the database migration or other mysql commands, could we also have a way to pass global parameters so we can handle --skip-ssl in the container?

[crazy-max]

Ok I was able to skip ssl entirely for the mysql client by using a global conf.