Issue: TLS Enforcement by MariaDB Client in Linux Alpine Base Image #54267
Unanswered
rayblair06
asked this question in
Ideas
Replies: 1 comment
-
a workaround that works globally is creating a my.cnf file containing the following
and add to your Dockerfile ADD ./path/to/my.cnf /etc/my.cnf |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey,
I've encountered an issue when mixing Linux Alpine as a base image with MySQL database instances. By default, the MariaDB client is used, which enforces TLS for database connections (see reference [1]). This creates a challenge when running commands with the
mysql
client (aliasmariadb
), particularly for tasks like importing squashed migrations.This issue seems to crop up when mixing MariaDB client with a MySQL database instance. While one proposed solution might be switching over to a MariaDB database instance, the reality is that mixing these two technologies isn’t uncommon. Plus, Linux Alpine is a popular choice for Docker base images, so this situation is likely to affect quite a few users.
Problem Details:
MySqlSchemaState
class (reference [2]) leverages themysql
client for some operations. This default TLS enforcement results in errors with no apparent way to override it.Proposed Solutions:
MySqlSchemaState
to handle this gracefully.Environment:
Reproduced Repo:
https://github.com/rayblair06/laravel-mariadb-11-4-bug
References:
Please let me know if more details are required. Happy to collaborate on resolving this!
Beta Was this translation helpful? Give feedback.
All reactions