Lando/Mysql8/Linux fail

[hlslaughter]

Linux system info:
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"

Lando version: v3.20.8

Using the same lando.yml our project has been using forever, I made these changes:

...
recipe: drupal10
...
services:
...
database:
type: mysql:8.0.22
...

• The result was a failed mysql8 startup and various oddities in the error logs. Examples:
• ✖ Healthcheck samalt3_database_1 FAILED
  ERROR ==> unknown shorthand flag: 'T' in -T
• [ERROR] [MY-013236] [Server] The designated data directory /bitnami/mysql/data/ is unusable. You can remove all files that the server added to it.
• And dozens of entries similar to this one, all regarding the files in /helpers:
  database_1 | chmod: changing permissions of '/helpers/psh-boot.sh': Operation not permitted

Some of the other devs tested this same config, and it seems to have worked. I'm the only one using Linux. The others use Macs. I'm guessing the whole Lando team uses Macs and so has not seen this issue.

After adding these configurations to the database service, I was able to get it to work:

services:
...
database:
...
run_as_root:
- mkdir -p /bitnami/mysql/data/
config:
database: .lando.mysql8.cnf

.lando.mysql8.cnf is a from https://github.com/AaronFeledy/lando-recipe-drupal9/blob/master/mysql.cnf with some deprecated values changed.

[GoonerW]

Is there a reason you're declaring the MySQL version under services: instead of config:?

I had a similar issue where MySQL wouldn't start due to removed settings in the config file and lando was using the "incorrect" one. The fix was made in the drupal10 recipe but I "think" lando only uses that fix if you use the drupal10 recipe to configure the database server and not explicitly declare it yourself.

See: lando/drupal#40 (comment)