Hello!

The new 3.17.0 version of lando seems to have issues with the JSONAPI Drupal core module (Drupal 10, latest version).

Symptom:

Jsonapi responds with an error:

"The following query parameters violate the JSON:API spec: 'q'."

How to reproduce

You could reproduce this by:

1. cloning this repository: https://github.com/wunderio/drupal-project (we use it at our company for all projects, it's been well tested)
2. make sure you have lando 3.17 installed
3. lando start && lando drush si -y && lando drush en jsonapi -y
4. visit https://drupal-project.lndo.site/jsonapi and witness the error.

Now, remove 3.17.0, reinstall 3.11, lando destroy and repeat the operations above, and jsonapi will work normally.

In another project of ours, where Drupal is installed in a subdirectory, we instead get a redirect loop at /jsonapi with 3.17.0, but all normal with 3.11.

This has been confirmed by a coworker with a different development machine.

I have found this issue in Drupal.org: https://www.drupal.org/project/jsonapi/issues/2984044 which refers to some configuration in nginx that jsonapi responds to by throwing this error. Was some default nginx configuration changed in this release?

Hope this helps!

The following fails, both when I try it with our example app and in the test suite:

lando drush si --db-url=mysql://drupal6:drupal6@database/drupal6 -y

...producing the error PHP Fatal error: Call to undefined function db_result() in phar:///usr/local/bin/drush/commands/core/drupal/site_install_6.inc on line 145

Presumably this means that drush si doesn't work with Drupal 6, at least in our context. I do know that others have had significant issues with this in the past, so it's very possible that there isn't really a great solution for using drush si with Drupal 6 any more. That's one reason I didn't pursue this further, but would be great to get other eyes on it :)

I recently tried switching one of my development sites using the Drupal 9 recipe from MySQL 5.7 (default) to MySQL 8.0 and the container failed to start. Looking at the logs the MySQL Service itself was erroring on the following configuration that Lando provides in its custom mysql.cnf file
query_cache_limit = 1M
query_cache_size = 64M
Query Cache has been removed completely from MySQL 8 (and was disabled by default back in MySQL 5.6) See this MySQL blog post for details.
Copying the template mysql.cnf file and loading it as a custom config file in Lando, commenting out the above two lines, allows the MySQL 8 container to then launch successfully.

Can we get an updated Drupal 9 and 10 recipe that removes those lines as they're no longer needed. Perhaps also suggest for the Drupal 10 recipe, that MySQL 8.0 be the default as MySQL 5.7 goes EoL in October 2023?

The drupal6 section seems to have drupal8 commands. that is all.

Hi there, I use Lando everyday at work with Drupal sites (Pantheon). Thank you for your work on Lando!

I feel like I am starting to see a pattern that whenever a new release comes out for Lando, my existing installed version stops working, and I am not able to run any of my existing sites until I install the latest version and initialise them again. Is there something to this? It could just be a coincidence and I am seeing causation where there is none, but it would be good to know if there is a definitive reason for this.

I am finding my productivity affected greatly that, periodically, using Lando that always works smoothly, suddenly stops working for all sites.

Platform
Windows 11
WSL2 Ubuntu 20.04.5 LTS

I am trying to execute lando pull and getting this result

lando -v pull --database=dev --code=none --files=none
lando 04:02:28 INFO ==> loading app APP_NAME from config files 0=/home/user/Projects/PROJECT_NAME/.lando.yml
? Choose a Pantheon account PANTHEON_EMAIL
lando 04:02:30 INFO ==> loading app APP_NAME from config files 0=/home/user/Projects/PROJECT_NAME/.lando.yml
Attempting to login via terminus...
 [notice] Logging in via machine token.
 [error]  HTTP request has failed with error "Maximum retry attempts reached".
 [error]  Could not find a saved token identified by .
 [error]  Please visit the dashboard to generate a machine token:
https://dashboard.pantheon.io/machine-token/create/PANTHEON_USER_ID

Tried to authorize via terminus auth:login in container (lando ssh):

[notice] Logging in via machine token.
[info] #### REQUEST ####
Headers: {"User-Agent":"Terminus/3.0.7 (php_version=7.4.33&script=/usr/local/bin/terminus)","Accept":"application/json","Content-Type":"application/json","Content-Length":85}
URI: https://terminus.pantheon.io:443/api/authorize/machine-token
Method: POST
Body: {"machine_token":"**HIDDEN**","client":"terminus"}
[warning] HTTP request POST https://terminus.pantheon.io/api/authorize/machine-token has failed: Connection refused for URI https://terminus.pantheon.io/api/authorize/machine-token
[warning] Retrying POST https://terminus.pantheon.io/api/authorize/machine-token 1 out of 5 (reason: Connection refused for URI https://terminus.pantheon.io/api/authorize/machine-token)
[warning] Retrying POST https://terminus.pantheon.io/api/authorize/machine-token 2 out of 5 (reason: Connection refused for URI https://terminus.pantheon.io/api/authorize/machine-token)
[warning] Retrying POST https://terminus.pantheon.io/api/authorize/machine-token 3 out of 5 (reason: Connection refused for URI https://terminus.pantheon.io/api/authorize/machine-token)
[warning] Retrying POST https://terminus.pantheon.io/api/authorize/machine-token 4 out of 5 (reason: Connection refused for URI https://terminus.pantheon.io/api/authorize/machine-token)
[error]  HTTP request has failed with error "Maximum retry attempts reached".

this php version has been deprecated and is no longer recommended

PostgreSQL should not be trying to install as I have nothing in my lando file asking for it.

Lando version: 3.1.4

.lando.yml:

name: myapp
recipe: drupal7
config:
  php: '7.3'
  composer_version: '2.4.4'
  via: apache:2.4
  webroot: .
  xdebug: true
  database: mysql:5.7
  config:
    php: .lando/php/php.ini

services:
  appserver:
    ssl: true
    build_as_root:
      - apt-get update
      - apt-get install -y libcurl4-openssl-dev libxml2-dev
      - printf "\n" | pecl install solr-2.5.1
      - docker-php-ext-enable solr
  pma:
    type: phpmyadmin
    hosts:
      - database

proxy:
  pma:
    - pma.myapp.lndo.site

The problematic part of the build output:

Get:1 http://security.debian.org/debian-security stretch/updates InRelease [59.1 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB]
Get:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [782 kB]
Ign:4 http://deb.debian.org/debian stretch InRelease       
Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [397 kB]
Get:6 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]    
Get:7 http://deb.debian.org/debian buster InRelease [122 kB]              
Get:8 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]          
Get:9 http://deb.debian.org/debian stretch Release [118 kB]
Get:10 http://deb.debian.org/debian stretch Release.gpg [3177 B]               
Get:11 http://deb.debian.org/debian buster/main amd64 Packages [7909 kB]
Get:12 http://deb.debian.org/debian buster-updates/main amd64 Packages [8788 B]
Get:13 http://deb.debian.org/debian stretch/main amd64 Packages [7080 kB]
Ign:14 http://apt.postgresql.org/pub/repos/apt stretch-pgdg InRelease          
Ign:15 http://apt.postgresql.org/pub/repos/apt stretch-pgdg Release
Ign:16 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main amd64 Packages
Ign:17 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main all Packages
Ign:16 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main amd64 Packages
Ign:17 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main all Packages
Ign:16 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main amd64 Packages
Ign:17 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main all Packages
Ign:16 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main amd64 Packages
Ign:17 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main all Packages
Ign:16 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main amd64 Packages
Ign:17 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main all Packages
Err:16 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main amd64 Packages
  404  Not Found [IP: 147.75.85.69 80]
Ign:17 http://apt.postgresql.org/pub/repos/apt stretch-pgdg/main all Packages
Fetched 16.7 MB in 3s (5271 kB/s)
Reading package lists... Done
W: The repository 'http://apt.postgresql.org/pub/repos/apt stretch-pgdg Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://apt.postgresql.org/pub/repos/apt/dists/stretch-pgdg/main/binary-amd64/Packages  404  Not Found [IP: 147.75.85.69 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
ERROR ==> E: Some index files failed to download. They have been ignored, or old ones used instead.

Drupal 10 requires composer 2.3.6 or higher so perhaps Composer should get updated? See also thinktandem/drupal-contributions#69.

https://www.drupal.org/node/3264830
And in drupal 9.5 release notes ity mentions the 8.1.x versioon going up because of an opcode cache bug

Hello for work correctly with Drupal 10 we should use at least Composer version 2.3.6 or higher, as suggest in the documentation

I try to install Drupal 10 as suggested in the lando recepit documentation, and if I install the dev repo composer version is set to 2.4.4, https://docs.lando.dev/drupal/getting-started.html:
lando composer create-project drupal/recommended-project:10.0.x-dev@dev tmp && cp -r tmp/. . && rm -rf tmp

but if i try to install the latest Drupal 10 version the composer version is 2.2.x, and I not find a correct way to override the composer version inside the .lando.yml
lando composer create-project drupal/recommended-project:10.x tmp && cp -r tmp/. . && rm -rf tmp

Here is my lando.yml file

name: d10-test
recipe: drupal10
excludes:
  - vendor
  - node_modules
  - modules/contrib
services:
  cache:
    type: redis
    persist: true
config:
  php: 8.2
  composer_version: 2-latest
  via: nginx
  webroot: web
tooling:
  redis-cli:
    service: cache

Drush 10 is EOL January 2022, and Drush 11 is "Supported and recommended" per Drupal Compatibility.

Merge Request: #5.

I am trying to run the lando composer install on mac and it is getting failed with the below exception.

Even i have increased the resource limit, ulimit -n 65535, but still getting the same error.

Could any one please help on the issue, i tried other version of lando installation but all failed with same issue when i run the lando composer install .

OS: SONOMA 14.4

Version details:

Composer version 2.7.2 2024-03-11 17:12:18
PHP version 8.1.27 (/usr/local/Cellar/[email protected]/8.1.27_1/bin/php)
lando : v3.21.0
Docker
Client:
Cloud integration: v1.0.35+desktop.4
Version: 24.0.6
Server: Docker Desktop 4.23.0 (120376)
Engine:
Version: 24.0.6

Exception logs

28/29 [===========================>] 96% Failed to extract drupal/core: (50) '/usr/bin/unzip' -qq '/app/vendor/composer/tmp-1667549757f9a6b12959e9e06fbfeb78' -d '/app/vendor/composer/24728b4f'

error: cannot create /app/vendor/composer/24728b4f/drupal-core-8afcb23/modules/book/src/Cache/BookNavigationCacheContext.php
Too many open files in system
checkdir error: cannot create /app/vendor/composer/24728b4f/drupal-core-8afcb23/modules/menu_ui/config/install
Too many open files in system
unable to process drupal-core-8afcb23/modules/menu_ui/config/install/.
error: cannot create /app/vendor/composer/24728b4f/drupal-core-8afcb23/modules/user/src/Controller/UserAuthenticationController.php
Too many open files in system
error: cannot create /app/vendor/composer/24728b4f/drupal-core-8afcb23/themes/olivero/templates/form/details.html.twig
Too many open files in system

The archive may contain identical file names with different capitalization (which fails on case insensitive filesystems)
Unzip with unzip command failed, falling back to ZipArchive class
Install of drupal/core failed

29/29 [============================] 100%

[RuntimeException]
The archive may contain identical file names with different capitalization (which fails on case insensitive filesystems): ZipArchive::extractTo(/app/vendor/composer/24728b4f/drupal-core-8afcb23/modules/ckeditor5/css/media-alignment.css): Failed to open stream: Too many open files in system

[ErrorException]
ZipArchive::extractTo(/app/vendor/composer/24728b4f/drupal-core-8afcb23/modules/ckeditor5/css/media-alignment.css): Failed to open stream: Too many open files in system

Anyone know how to setup a chromedriver to test FunctionalJavascript files ?

Installed proceed to install the lando arm64 version on x64 resulting in bad CPU error on application start as below
zsh: bad CPU type in executable: lando

I'm working with Lando v3.21.0-beta.12. And I think issue started after update to this version.

After lando start on my Drupal app I'm getting this message

Failed with "mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2003 (HY000): Can't connect to MySQL server on 'database' (111)"

After lando logs -s database I get this:

➜ d10-minimal lando logs -s database
database_1 |
database_1 |
database_1 |
database_1 | STARTING UP
database_1 |
database_1 | ██  █████  ███  ██ ██████  ██████ 
database_1 | ██  ██   ██ ████  ██ ██   ██ ██    ██ 
database_1 | ██  ███████ ██ ██  ██ ██  ██ ██  ██ 
database_1 | ██  ██   ██ ██  ██ ██ ██  ██ ██  ██ 
database_1 | ███████ ██  ██ ██   ████ ██████   ██████  
database_1 |
database_1 | The best local development tool in the galaxy!
database_1 |
database_1 |
database_1 | ===============================================================
database_1 |
database_1 |
database_1 | userperms 06:27:23.78 WARN ==> Only the root user can reset permissions! This is probably ok though...
database_1 | loadkeys 06:27:23.79 WARN ==> Only the root user can load ssh keys! This is probably ok though...
database_1 | lando 06:27:23.80 INFO ==> Lando handing off to: /launch.sh
database_1 | lando 06:27:23.80 DEBUG ==> Running command with exec...
database_1 | mysql 06:27:23.90
database_1 | mysql 06:27:23.91 Welcome to the Bitnami mysql container
database_1 | mysql 06:27:23.91 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mysql
database_1 | mysql 06:27:23.91 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mysql/issues
database_1 | mysql 06:27:23.91 Send us your feedback at [email protected]
database_1 | mysql 06:27:23.91
database_1 | mysql 06:27:23.91 INFO ==> ** Starting MySQL setup **
database_1 | mysql 06:27:23.98 INFO ==> Validating settings in MYSQL_/MARIADB_ env vars
database_1 | mysql 06:27:23.99 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
database_1 | mysql 06:27:24.00 INFO ==> Initializing mysql database
database_1 | mysql 06:27:24.01 DEBUG ==> Injecting custom configuration from my_custom.conf
database_1 | mysql 06:27:24.02 DEBUG ==> Ensuring expected directories/files exist
database_1 | mysql 06:27:24.03 DEBUG ==> Creating main configuration file
database_1 | mysql 06:27:24.03 INFO ==> Using persisted data
database_1 | mysql 06:27:24.05 INFO ==> Running mysql_upgrade
database_1 | mysql 06:27:24.06 INFO ==> Starting mysql in background
database_1 | 2024-04-02T06:27:24.267989Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
database_1 | 2024-04-02T06:27:24.268056Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 157 ...
database_1 | 2024-04-02T06:27:24.338693Z 0 [Note] InnoDB: PUNCH HOLE support available
database_1 | 2024-04-02T06:27:24.338742Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1 | 2024-04-02T06:27:24.338747Z 0 [Note] InnoDB: Uses event mutexes
database_1 | 2024-04-02T06:27:24.338748Z 0 [Note] InnoDB: GCC builtin atomic_thread_fence() is used for memory barrier
database_1 | 2024-04-02T06:27:24.338750Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
database_1 | 2024-04-02T06:27:24.338752Z 0 [Note] InnoDB: Using Linux native AIO
database_1 | 2024-04-02T06:27:24.338936Z 0 [Note] InnoDB: Number of pools: 1
database_1 | 2024-04-02T06:27:24.339066Z 0 [Note] InnoDB: Using CPU crc32 instructions
database_1 | 2024-04-02T06:27:24.341458Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
database_1 | 2024-04-02T06:27:24.366578Z 0 [Note] InnoDB: Completed initialization of buffer pool
database_1 | 2024-04-02T06:27:24.372986Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
database_1 | 2024-04-02T06:27:24.390603Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
database_1 | 2024-04-02T06:27:24.422358Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 66453270
database_1 | 2024-04-02T06:27:24.422398Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 66453279
database_1 | 2024-04-02T06:27:24.422404Z 0 [Note] InnoDB: Database was not shutdown normally!
database_1 | 2024-04-02T06:27:24.422406Z 0 [Note] InnoDB: Starting crash recovery.
database_1 | 2024-04-02T06:27:24.646182Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
database_1 | 2024-04-02T06:27:24.646449Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
database_1 | 2024-04-02T06:27:24.646627Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
database_1 | 2024-04-02T06:27:24.646706Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
database_1 | 2024-04-02T06:27:24.646752Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
database_1 | 2024-04-02T06:27:24.646758Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
database_1 | 2024-04-02T06:27:24.646762Z 0 [ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space
database_1 | 2024-04-02T06:27:24.646764Z 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
database_1 | 2024-04-02T06:27:24.646766Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
database_1 | 2024-04-02T06:27:25.147831Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
database_1 | 2024-04-02T06:27:25.147917Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
database_1 | 2024-04-02T06:27:25.147923Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
database_1 | 2024-04-02T06:27:25.147927Z 0 [ERROR] Failed to initialize builtin plugins.
database_1 | 2024-04-02T06:27:25.147928Z 0 [ERROR] Aborting
database_1 |
database_1 | 2024-04-02T06:27:25.147931Z 0 [Note] Binlog end
database_1 | 2024-04-02T06:27:25.147969Z 0 [Note] Shutting down plugin 'CSV'
database_1 | 2024-04-02T06:27:25.153716Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: Shutdown complete
database_1 |
database_1 | userperms 06:31:40.29 WARN ==> Only the root user can reset permissions! This is probably ok though...
database_1 | loadkeys 06:31:40.32 WARN ==> Only the root user can load ssh keys! This is probably ok though...
database_1 | lando 06:31:40.32 INFO ==> Lando handing off to: /launch.sh
database_1 | lando 06:31:40.33 DEBUG ==> Running command with exec...
database_1 | mysql 06:31:40.43
database_1 | mysql 06:31:40.43 Welcome to the Bitnami mysql container
database_1 | mysql 06:31:40.43 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mysql
database_1 | mysql 06:31:40.43 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mysql/issues
database_1 | mysql 06:31:40.43 Send us your feedback at [email protected]
database_1 | mysql 06:31:40.43
database_1 | mysql 06:31:40.44 INFO ==> ** Starting MySQL setup **
database_1 | mysql 06:31:40.53 INFO ==> Validating settings in MYSQL*/MARIADB* env vars
database_1 | mysql 06:31:40.53 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
database_1 | mysql 06:31:40.54 INFO ==> Initializing mysql database
database_1 | mysql 06:31:40.54 DEBUG ==> Injecting custom configuration from my_custom.conf
database_1 | mysql 06:31:40.55 DEBUG ==> Custom configuration my.cnf detected
database_1 | mysql 06:31:40.55 DEBUG ==> Ensuring expected directories/files exist
database_1 | mysql 06:31:40.57 INFO ==> Using persisted data
database_1 | mysql 06:31:40.61 INFO ==> Running mysql_upgrade
database_1 | mysql 06:31:40.61 INFO ==> Starting mysql in background
database_1 | 2024-04-02T06:31:40.978495Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
database_1 | 2024-04-02T06:31:40.979381Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 155 ...
database_1 | 2024-04-02T06:31:41.128367Z 0 [Note] InnoDB: PUNCH HOLE support available
database_1 | 2024-04-02T06:31:41.128389Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1 | 2024-04-02T06:31:41.128391Z 0 [Note] InnoDB: Uses event mutexes
database_1 | 2024-04-02T06:31:41.128393Z 0 [Note] InnoDB: GCC builtin atomic_thread_fence() is used for memory barrier
database_1 | 2024-04-02T06:31:41.128395Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
database_1 | 2024-04-02T06:31:41.128397Z 0 [Note] InnoDB: Using Linux native AIO
database_1 | 2024-04-02T06:31:41.129872Z 0 [Note] InnoDB: Number of pools: 1
database_1 | 2024-04-02T06:31:41.131720Z 0 [Note] InnoDB: Using CPU crc32 instructions
database_1 | 2024-04-02T06:31:41.136840Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
database_1 | 2024-04-02T06:31:41.200043Z 0 [Note] InnoDB: Completed initialization of buffer pool
database_1 | 2024-04-02T06:31:41.216736Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
database_1 | 2024-04-02T06:31:41.236533Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
database_1 | 2024-04-02T06:31:41.241489Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 66453270
database_1 | 2024-04-02T06:31:41.241580Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 66453279
database_1 | 2024-04-02T06:31:41.241614Z 0 [Note] InnoDB: Database was not shutdown normally!
database_1 | 2024-04-02T06:31:41.241632Z 0 [Note] InnoDB: Starting crash recovery.
database_1 | 2024-04-02T06:31:41.479711Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
database_1 | 2024-04-02T06:31:41.479764Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
database_1 | 2024-04-02T06:31:41.481099Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
database_1 | 2024-04-02T06:31:41.481131Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
database_1 | 2024-04-02T06:31:41.481147Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
database_1 | 2024-04-02T06:31:41.481193Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
database_1 | 2024-04-02T06:31:41.481201Z 0 [ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space
database_1 | 2024-04-02T06:31:41.481205Z 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
database_1 | 2024-04-02T06:31:41.481208Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
database_1 | 2024-04-02T06:31:41.881920Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
database_1 | 2024-04-02T06:31:41.882034Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
database_1 | 2024-04-02T06:31:41.882041Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
database_1 | 2024-04-02T06:31:41.882046Z 0 [ERROR] Failed to initialize builtin plugins.
database_1 | 2024-04-02T06:31:41.882048Z 0 [ERROR] Aborting
database_1 |
database_1 | 2024-04-02T06:31:41.882059Z 0 [Note] Binlog end
database_1 | 2024-04-02T06:31:41.882395Z 0 [Note] Shutting down plugin 'CSV'
database_1 | 2024-04-02T06:31:41.889624Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: Shutdown complete
database_1 |
database_1 | userperms 08:37:29.60 WARN ==> Only the root user can reset permissions! This is probably ok though...
database_1 | loadkeys 08:37:29.62 WARN ==> Only the root user can load ssh keys! This is probably ok though...
database_1 | lando 08:37:29.62 INFO ==> Lando handing off to: /launch.sh
database_1 | lando 08:37:29.62 DEBUG ==> Running command with exec...
database_1 | mysql 08:37:29.71
database_1 | mysql 08:37:29.71 Welcome to the Bitnami mysql container
database_1 | mysql 08:37:29.71 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mysql
database_1 | mysql 08:37:29.72 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mysql/issues
database_1 | mysql 08:37:29.72 Send us your feedback at [email protected]
database_1 | mysql 08:37:29.72
database_1 | mysql 08:37:29.73 INFO ==> ** Starting MySQL setup **
database_1 | mysql 08:37:29.82 INFO ==> Validating settings in MYSQL*/MARIADB* env vars
database_1 | mysql 08:37:29.82 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
database_1 | mysql 08:37:29.83 INFO ==> Initializing mysql database
database_1 | mysql 08:37:29.83 DEBUG ==> Injecting custom configuration from my_custom.conf
database_1 | mysql 08:37:29.84 DEBUG ==> Custom configuration my.cnf detected
database_1 | mysql 08:37:29.85 DEBUG ==> Ensuring expected directories/files exist
database_1 | mysql 08:37:29.87 INFO ==> Using persisted data
database_1 | mysql 08:37:29.92 INFO ==> Running mysql_upgrade
database_1 | mysql 08:37:29.93 INFO ==> Starting mysql in background
database_1 | 2024-04-02T08:37:30.292445Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
database_1 | 2024-04-02T08:37:30.293917Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 154 ...
database_1 | 2024-04-02T08:37:30.438852Z 0 [Note] InnoDB: PUNCH HOLE support available
database_1 | 2024-04-02T08:37:30.438904Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1 | 2024-04-02T08:37:30.438909Z 0 [Note] InnoDB: Uses event mutexes
database_1 | 2024-04-02T08:37:30.438911Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1 | 2024-04-02T08:37:30.438913Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
database_1 | 2024-04-02T08:37:30.438915Z 0 [Note] InnoDB: Using Linux native AIO
database_1 | 2024-04-02T08:37:30.441037Z 0 [Note] InnoDB: Number of pools: 1
database_1 | 2024-04-02T08:37:30.443799Z 0 [Note] InnoDB: Using CPU crc32 instructions
database_1 | 2024-04-02T08:37:30.450203Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
database_1 | 2024-04-02T08:37:30.518720Z 0 [Note] InnoDB: Completed initialization of buffer pool
database_1 | 2024-04-02T08:37:30.540219Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
database_1 | 2024-04-02T08:37:30.559242Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
database_1 | 2024-04-02T08:37:30.566343Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 66453270
database_1 | 2024-04-02T08:37:30.566542Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 66453279
database_1 | 2024-04-02T08:37:30.566586Z 0 [Note] InnoDB: Database was not shutdown normally!
database_1 | 2024-04-02T08:37:30.566590Z 0 [Note] InnoDB: Starting crash recovery.
database_1 | 2024-04-02T08:37:30.898564Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
database_1 | 2024-04-02T08:37:30.898880Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
database_1 | 2024-04-02T08:37:30.920911Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
database_1 | 2024-04-02T08:37:30.921931Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
database_1 | 2024-04-02T08:37:30.921941Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
database_1 | 2024-04-02T08:37:30.924138Z 0 [Note] InnoDB: 5.7.29 started; log sequence number 66453279
database_1 | 2024-04-02T08:37:30.926222Z 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mysql/data/ib_buffer_pool
database_1 | 2024-04-02T08:37:30.929445Z 0 [Note] Plugin 'FEDERATED' is disabled.
database_1 | 2024-04-02T08:37:30.957289Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
database_1 | 2024-04-02T08:37:30.957363Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
database_1 | 2024-04-02T08:37:30.961284Z 0 [Warning] CA certificate ca.pem is self signed.
database_1 | 2024-04-02T08:37:30.961361Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
database_1 | 2024-04-02T08:37:30.962340Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
database_1 | 2024-04-02T08:37:30.962731Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
database_1 | 2024-04-02T08:37:30.962835Z 0 [Note] Server socket created on IP: '127.0.0.1'.
database_1 | 2024-04-02T08:37:30.969069Z 0 [Note] InnoDB: Buffer pool(s) load completed at 240402 8:37:30
database_1 | 2024-04-02T08:37:31.038238Z 0 [Note] Event Scheduler: Loaded 0 events
database_1 | 2024-04-02T08:37:31.039328Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: ready for connections.
database_1 | Version: '5.7.29' socket: '/opt/bitnami/mysql/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
database_1 | Checking server version.
database_1 | Running queries to upgrade MySQL server.
database_1 | Checking system database.
database_1 | mysql.columns_priv OK
database_1 | mysql.db OK
database_1 | mysql.engine_cost OK
database_1 | mysql.event OK
database_1 | mysql.func OK
database_1 | mysql.general_log OK
database_1 | mysql.gtid_executed OK
database_1 | mysql.help_category OK
database_1 | mysql.help_keyword OK
database_1 | mysql.help_relation OK
database_1 | mysql.help_topic OK
database_1 | mysql.innodb_index_stats OK
database_1 | mysql.innodb_table_stats OK
database_1 | mysql.ndb_binlog_index OK
database_1 | mysql.plugin OK
database_1 | mysql.proc OK
database_1 | mysql.procs_priv OK
database_1 | mysql.proxies_priv OK
database_1 | mysql.server_cost OK
database_1 | mysql.servers OK
database_1 | mysql.slave_master_info OK
database_1 | mysql.slave_relay_log_info OK
database_1 | mysql.slave_worker_info OK
database_1 | mysql.slow_log OK
database_1 | mysql.tables_priv OK
database_1 | mysql.time_zone OK
database_1 | mysql.time_zone_leap_second OK
database_1 | mysql.time_zone_name OK
database_1 | mysql.time_zone_transition OK
database_1 | mysql.time_zone_transition_type OK
database_1 | mysql.user OK
database_1 | The sys schema is already up to date (version 1.5.2).
database_1 | Checking databases.
database_1 | drupal10.batch OK
database_1 | drupal10.cache_bootstrap OK
database_1 | drupal10.cache_config OK
database_1 | drupal10.cache_container OK
database_1 | drupal10.cache_data OK
database_1 | drupal10.cache_default OK
database_1 | drupal10.cache_discovery OK
database_1 | drupal10.cache_dynamic_page_cache OK
database_1 | drupal10.cache_entity OK
database_1 | drupal10.cache_menu OK
database_1 | drupal10.cache_render OK
database_1 | drupal10.cachetags OK
database_1 | drupal10.comment OK
database_1 | drupal10.comment__comment_body OK
database_1 | drupal10.comment__field_stick_comment_on_top_boole OK
database_1 | drupal10.comment__stick_on_top_by_likes OK
database_1 | drupal10.comment_entity_statistics OK
database_1 | drupal10.comment_field_data OK
database_1 | drupal10.config OK
database_1 | drupal10.help_search_items OK
database_1 | drupal10.key_value OK
database_1 | drupal10.key_value_expire OK
database_1 | drupal10.menu_tree OK
database_1 | drupal10.node OK
database_1 | drupal10.node__body OK
database_1 | drupal10.node_access OK
database_1 | drupal10.node_field_data OK
database_1 | drupal10.node_field_revision OK
database_1 | drupal10.node_revision OK
database_1 | drupal10.node_revision__body OK
database_1 | drupal10.path_alias OK
database_1 | drupal10.path_alias_revision OK
database_1 | drupal10.queue OK
database_1 | drupal10.router OK
database_1 | drupal10.semaphore OK
database_1 | drupal10.sequences OK
database_1 | drupal10.sessions OK
database_1 | drupal10.user__roles OK
database_1 | drupal10.users OK
database_1 | drupal10.users_data OK
database_1 | drupal10.users_field_data OK
database_1 | drupal10.watchdog OK
database_1 | sys.sys_config OK
database_1 | Upgrade process completed successfully.
database_1 | Checking if update is needed.
database_1 | mysql 08:37:33.17 INFO ==> Stopping mysql
database_1 | 2024-04-02T08:37:33.176906Z 0 [Note] Giving 0 client threads a chance to die gracefully
database_1 | 2024-04-02T08:37:33.176965Z 0 [Note] Shutting down slave threads
database_1 | 2024-04-02T08:37:33.176979Z 0 [Note] Forcefully disconnecting 0 remaining clients
database_1 | 2024-04-02T08:37:33.176984Z 0 [Note] Event Scheduler: Purging the queue. 0 events
database_1 | 2024-04-02T08:37:33.177397Z 0 [Note] Binlog end
database_1 | 2024-04-02T08:37:33.177875Z 0 [Note] Shutting down plugin 'ngram'
database_1 | 2024-04-02T08:37:33.177929Z 0 [Note] Shutting down plugin 'partition'
database_1 | 2024-04-02T08:37:33.177935Z 0 [Note] Shutting down plugin 'BLACKHOLE'
database_1 | 2024-04-02T08:37:33.177937Z 0 [Note] Shutting down plugin 'ARCHIVE'
database_1 | 2024-04-02T08:37:33.177939Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
database_1 | 2024-04-02T08:37:33.177953Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
database_1 | 2024-04-02T08:37:33.177954Z 0 [Note] Shutting down plugin 'MyISAM'
database_1 | 2024-04-02T08:37:33.177960Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
database_1 | 2024-04-02T08:37:33.177961Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
database_1 | 2024-04-02T08:37:33.177962Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
database_1 | 2024-04-02T08:37:33.177964Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
database_1 | 2024-04-02T08:37:33.177965Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
database_1 | 2024-04-02T08:37:33.177966Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
database_1 | 2024-04-02T08:37:33.177967Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
database_1 | 2024-04-02T08:37:33.177968Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
database_1 | 2024-04-02T08:37:33.177969Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
database_1 | 2024-04-02T08:37:33.177970Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
database_1 | 2024-04-02T08:37:33.177971Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
database_1 | 2024-04-02T08:37:33.177972Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
database_1 | 2024-04-02T08:37:33.177973Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
database_1 | 2024-04-02T08:37:33.177974Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
database_1 | 2024-04-02T08:37:33.177975Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
database_1 | 2024-04-02T08:37:33.177976Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
database_1 | 2024-04-02T08:37:33.177977Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
database_1 | 2024-04-02T08:37:33.177978Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
database_1 | 2024-04-02T08:37:33.177979Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
database_1 | 2024-04-02T08:37:33.177980Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
database_1 | 2024-04-02T08:37:33.177981Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
database_1 | 2024-04-02T08:37:33.177982Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
database_1 | 2024-04-02T08:37:33.177983Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
database_1 | 2024-04-02T08:37:33.177984Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
database_1 | 2024-04-02T08:37:33.177985Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
database_1 | 2024-04-02T08:37:33.177986Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
database_1 | 2024-04-02T08:37:33.177987Z 0 [Note] Shutting down plugin 'INNODB_CMP'
database_1 | 2024-04-02T08:37:33.177988Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
database_1 | 2024-04-02T08:37:33.177988Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
database_1 | 2024-04-02T08:37:33.177990Z 0 [Note] Shutting down plugin 'INNODB_TRX'
database_1 | 2024-04-02T08:37:33.177991Z 0 [Note] Shutting down plugin 'InnoDB'
database_1 | 2024-04-02T08:37:33.178254Z 0 [Note] InnoDB: FTS optimize thread exiting.
database_1 | 2024-04-02T08:37:33.178569Z 0 [Note] InnoDB: Starting shutdown...
database_1 | 2024-04-02T08:37:33.279053Z 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mysql/data/ib_buffer_pool
database_1 | 2024-04-02T08:37:33.279318Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 240402 8:37:33
database_1 | 2024-04-02T08:37:34.791673Z 0 [Note] InnoDB: Shutdown completed; log sequence number 66539172
database_1 | 2024-04-02T08:37:34.791796Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
database_1 | 2024-04-02T08:37:34.791808Z 0 [Note] Shutting down plugin 'MEMORY'
database_1 | 2024-04-02T08:37:34.791812Z 0 [Note] Shutting down plugin 'CSV'
database_1 | 2024-04-02T08:37:34.791814Z 0 [Note] Shutting down plugin 'sha256_password'
database_1 | 2024-04-02T08:37:34.791816Z 0 [Note] Shutting down plugin 'mysql_native_password'
database_1 | 2024-04-02T08:37:34.791898Z 0 [Note] Shutting down plugin 'binlog'
database_1 | 2024-04-02T08:37:34.796656Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: Shutdown complete
database_1 |
database_1 |
database_1 | mysql 08:37:35.18 INFO ==> ** MySQL setup finished! **
database_1 | mysql 08:37:35.25 INFO ==> ** Starting MySQL **
database_1 | 2024-04-02T08:37:35.422730Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
database_1 | 2024-04-02T08:37:35.422790Z 0 [Note] /opt/bitnami/mysql/bin/mysqld (mysqld 5.7.29) starting as process 16 ...
database_1 | 2024-04-02T08:37:35.455983Z 0 [Note] InnoDB: PUNCH HOLE support available
database_1 | 2024-04-02T08:37:35.456028Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1 | 2024-04-02T08:37:35.456033Z 0 [Note] InnoDB: Uses event mutexes
database_1 | 2024-04-02T08:37:35.456035Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1 | 2024-04-02T08:37:35.456037Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
database_1 | 2024-04-02T08:37:35.456039Z 0 [Note] InnoDB: Using Linux native AIO
database_1 | 2024-04-02T08:37:35.456344Z 0 [Note] InnoDB: Number of pools: 1
database_1 | 2024-04-02T08:37:35.456488Z 0 [Note] InnoDB: Using CPU crc32 instructions
database_1 | 2024-04-02T08:37:35.458006Z 0 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
database_1 | 2024-04-02T08:37:35.480037Z 0 [Note] InnoDB: Completed initialization of buffer pool
database_1 | 2024-04-02T08:37:35.484644Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
database_1 | 2024-04-02T08:37:35.497766Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
database_1 | 2024-04-02T08:37:35.540782Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
database_1 | 2024-04-02T08:37:35.540886Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
database_1 | 2024-04-02T08:37:35.552540Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
database_1 | 2024-04-02T08:37:35.553181Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
database_1 | 2024-04-02T08:37:35.553214Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
database_1 | 2024-04-02T08:37:35.554011Z 0 [Note] InnoDB: 5.7.29 started; log sequence number 66539172
database_1 | 2024-04-02T08:37:35.554417Z 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mysql/data/ib_buffer_pool
database_1 | 2024-04-02T08:37:35.554605Z 0 [Note] Plugin 'FEDERATED' is disabled.
database_1 | 2024-04-02T08:37:35.559002Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
database_1 | 2024-04-02T08:37:35.559035Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
database_1 | 2024-04-02T08:37:35.559516Z 0 [Warning] CA certificate ca.pem is self signed.
database_1 | 2024-04-02T08:37:35.559579Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
database_1 | 2024-04-02T08:37:35.559651Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
database_1 | 2024-04-02T08:37:35.559684Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
database_1 | 2024-04-02T08:37:35.559712Z 0 [Note] Server socket created on IP: '127.0.0.1'.
database_1 | 2024-04-02T08:37:35.570197Z 0 [Note] Event Scheduler: Loaded 0 events
database_1 | 2024-04-02T08:37:35.570813Z 0 [Note] /opt/bitnami/mysql/bin/mysqld: ready for connections.
database_1 | Version: '5.7.29' socket: '/opt/bitnami/mysql/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
database_1 | 2024-04-02T08:37:35.573356Z 0 [Note] InnoDB: Buffer pool(s) load completed at 240402 8:37:35

It is not problem with disk space I have more than 500 GB

##Steps to reproduce:

1. Create a new drupal 9 recipe using lando init command.
2. Update .lando.yml file to use php8 and enable xdebug as shown below in config

config:
  webroot: docroot
  php: '8.0'
  xdebug: debug

3. Now ssh on to the lando container, and check for php version php --version

#Expected Output of the above command:
The above command should output php version with details of xdebug version/

#Actual output we get :

PHP 8.0.23 (cli) (built: Sep  1 2022 22:06:18) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.23, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.23, Copyright (c), by Zend Technologies

If I rebuild the container php7.4 xdebug gets installed and the output is as below:

PHP 7.4.30 (cli) (built: Aug 23 2022 15:23:34) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.30, Copyright (c), by Zend Technologies
    with Xdebug v3.1.5, Copyright (c) 2002-2022, by Derick Rethans

As Drupal 9 and above support and requires php 8, I am unable debug code using xdebug if I am using php8.

Drush 10 is EOL, so Drush 11 is required, see https://www.drush.org/latest/install/#drupal-compatibility. Also:

Drush 11 required for Drupal 10
Drush 10 has a dependency that requires Twig 1 or Twig 2 so is incompatible with Drupal 10, making Drush 11 required.

From Change record Twig updated from 2.x to 3.x.

For PHP and database versions, see [meta] Set Drupal 10 platform and browser requirements and Gather data to support potentially requiring PHP 8.1 in Drupal 10.0 or later.

Merge Request: #3.

I've been using this for some time now without any issues:

lando init \
  --recipe drupal7 \
  --webroot . \
  --name d7test \
  --option database=mariadb \

lando start
lando drush -y si standard --db-url=mysql://drupal7:drupal7@database:3306/drupal7 --site-name="D7 test site" --account-pass=password

But I recently started having issues:

You are about to create a /app/sites/default/settings.php file and CREATE the 'drupal7' database.
Do you want to continue? (y/n): y
Failed to create database: ERROR 2002 (HY000): Can't connect to MySQL server on 'database' (115)
[error]

I then noticed a couple of these php-related warnings:

...
Oh... and here are some vitals:

 NAME      d7test
 LOCATION  /Users/greg/drupal/d7test   
 RECIPE    drupal7                                    
 DOCS      https://docs.lando.dev/config/drupal7.html 

php version 7.2 is a legacy version! We recommend upgrading.
Let's get this party started! Starting app d7test...
php version 7.2 is a legacy version! We recommend upgrading.
landoproxyhyperion5000gandalfedition_proxy_1 is up-to-date
...

So I updated the init command to include --option php=7.4 and things started working as expected again. Not sure if this is because D7 requires an updated version of php now(?), or if it is lando-specific, but if you update the D7 recipe to use php 7.4 by default, then this issue is solved.

Hi, I have encountered a problem using this module on Drupal https://www.drupal.org/project/s3fs.

It seems to be missing some requirements for the module to work properly.

https://www.drupal.org/project/s3fs/issues/3413499#comment-15390486

Upon lando start, I get this error- ERROR ==> Error: (HTTP code 404) no such container - No such container: landoproxyhyperion5000gandalfedition_proxy_1
I do have that container in my docker desktop. ANyone has an idea about it?

While using the Drupal 9 recipe, my known hosts file gets clobbered every time I restart. I'm left with a broken symlink owned by root.

I found a similar issue, but it is from a couple years ago and was unresolved: lando/lando#2278

I have gone through my config and can not find anything custom that would be causing this, so I'm looking for ideas and/or work-arounds.

Is it possible to get Xdebug and Sublime Text 4 working in Lando? There are Guides on PhpStorm and VSCode and a similar solution on how to get it working with Sublime Text 4 and SublimeTextXdebug would be awesome. Thanks!

PS. Install SublimeTextXdebug with Git, see Can't install via Package Control in Sublime Text 4 #210 .

After Drupal 10.2.0, drupal supports Php 8.3

Lando PHP got 8.3 support. Please update drupal-php to support PHP 8.3 accordingly.

node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Error: drupal-php version 8.3 is not supported

Thank you

Hello,

I'm updating projects between Drupal 8 and 9 versions and I'm struggling with the database.

If I update the recipe to Drupal 9 and do lando rebuild it will keep Drupal 8 credentials but if a new dev joins (or I need to destroy the project and start it again) it will create the database credentials with drupal9.

Since the Drupal release cycle is speeding up since Drupal 9 (Drupal 10 is expected to be in June 2022) will it be a good idea to just have "drupal" as credential to every Drupal recipe (or just the future ones) out of the box.

Thanks

This might not be limited to Drupal recipes:

When entering the appserver container (lando ssh), or issuing Drush commands (lando drush) there's no supprt for special chars, e.g. German umlauts. The reason is, that the container's locale is set to POSIX:

www-data@ad5a078ae96d:/app$ locale
LANG=
LANGUAGE=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
www-data@ad5a078ae96d:/app$

I'd expect to see a locale based on UTF-8, like en_US.UTF-8. Is this an issue with the upstream Bitnami images? And how can it be fixed?

If you use the drupal/s3fs module (https://www.drupal.org/project/s3fs) with image styles, it changes all the image styles paths to start with /s3/files/styles/....

The current vhost default.conf file doesn't allow for generating image styles using that path, making all the image styles 404

Current (doesn't support S3FS module + image styles)

  # Fighting with Styles? This little gem is amazing.
  # location ~ ^/sites/.*/files/imagecache/ { # For Drupal <= 6
  location ~ ^(/[a-z\-]+)?/sites/.*/files/styles/ { # For Drupal >= 7
      try_files $uri @rewrite;
  }

After much debugging for finding the root cause, I did the following and it works now. I don't know if it's the best way, but just thought I'd share if someone would want to contribute and commit into the recipe.

Fixed (at least for me)

  # Fighting with Styles? This little gem is amazing.
  # location ~ ^/sites/.*/files/imagecache/ { # For Drupal <= 6
  location ~ '^(/[a-z\-]+)?/sites/.*/files/styles/|^/s3/files/styles/' { # For Drupal >= 7
      try_files $uri @rewrite;
  }

Hello.

Following Lando Official Guide Steps, we went to this step and the issue occured:
=>lando drush site:install --db-url=mysql://drupal10:drupal10@database/drupal10 -y
=>[preflight] Package "drupal/core" is not installed

This is an unexpected output.

Environment:

1. Latest Lando with its built-in Docker // v3.21.0-beta.1
2. Macbook M1Pro Chip; project folder "b6". please refer to the attachment.

I have an issue when i start my application running the command "lando start" at home, as the example.lndo.site URLs appear on red and the project is not available to view in the browser, however, when i do the same using my company's internal ethernet connection the project launches without any issue

Using version 3.19.5 and 3.18.0 (I have not tested other older versions) Drupal 7 recipe fails to give 200 response.

I have no issues with D9 or D10 recipes.

Hi All,

First, I'm completely new to this and don't know where to start to ask for help. I think I screwed up my Lando/Docker installation. When trying to execute a commands in Docker, I have to specify "Lando Start" or "Lando Info" for example instead of "Start" or "Info"

I was working in Drupal and was using Bartik as my theme and I switched to Zen, and am now getting a "The website encountered an unexpected error. Please try again later." error message and cannot access anything on my site. This is the only message I am receiving. I am very new to Drupal and was tried to see what would happen if I tried to apply an unsupported theme, like Zen, and am finding out the hard way!!! I thought perhaps an "error" message would have come up somewhere, but I was wrong....

I tried "drush config-set system.theme admin bartik" and am getting an "OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "drush": executable file not found in $PATH: unknown" error message.

I also cannot access "/admin/reports/dblog" either.

Help! Thanks in advance!

After upgrading lando to 3.20.7 from 3.20.6 I get the following error when doing a lando rebuild -y

WARN ==> drupal8 is not a supported recipe type.
ERROR ==> Could not find a service builder called drupal8 in the builder registry!

The recipe is drupal8, I've also tried drupal10 (since the project has been upgraded in the meantime) but to no result.

Lando file:

name: myproject
recipe: drupal8
config:
  php: '8.1'
  composer_version: '2.6.5'
  via: apache
  database: mysql
  drush: ^8
  xdebug: false
  webroot: web

System: Ubuntu 22.04.3 LTS
Docker 24.0.7, build afdd53b

When using the drupal10 recipe with nginx and Drupal 10.1 I am unable to access CSS and JS when preprocessing / aggregation is enabled.

Example config:

recipe: drupal10
config:
  via: nginx

This is the same issue that was closed against Drupal core as being down to outdated nginx config https://www.drupal.org/project/drupal/issues/3368769

https://github.com/lando/drupal/blob/main/recipes/drupal10/default.conf.tpl#L57

has

  location @rewrite {
      rewrite ^/(.*)$ /index.php?q=$1;
  }

Where the nginx example config has

  location @rewrite {
      #rewrite ^/(.*)$ /index.php?q=$1; # For Drupal <= 6
      rewrite ^ /index.php; # For Drupal >= 7
  }

I have tested this change locally using config override on the appservice and it fixed the issue I was experiencing.

MR incoming

When I try to run any drush command I get an error with the drupal10 recipe.
I get the following error using -vvv option:

  lando emitting event ready  +7ms
  lando emitting event cli-answers  +1ms
  lando emitting event cli-drush-answers  +0ms
  lando emitting event cli-run  +0ms
  lando emitting event cli-drush-run  +1ms
  lando resolved tooling command drush service to app  +2ms
  lando emitting event pre-command-runner  +0ms
  lando emitting event pre-drush  +1ms
  lando ERROR TypeError: Cannot read properties of undefined (reading 'match')
    at parse (/snapshot/cli/node_modules/@lando/core/node_modules/yargs-parser/index.js:154:13)
    at Parser (/snapshot/cli/node_modules/@lando/core/node_modules/yargs-parser/index.js:855:16)
    at Shell.sh (/snapshot/cli/node_modules/@lando/core/lib/shell.js)
    at /snapshot/cli/node_modules/@lando/core/utils/build-docker-exec.js
    at /snapshot/cli/node_modules/@lando/core/utils/build-tooling-task.js
    at process.processImmediate (node:internal/timers:476:21)  +5ms

.lando.yml content:

name: test
recipe: drupal10
config:
  webroot: web

Drush version in composer: 11.6.0
Lando version: v3.21.0
All plugin are up to date.

Your PHP installation is too old. Refer to the Drupal PHP requirements for the currently recommended PHP version for this release. See PHP's version support documentation for more information on PHP's own support schedule.

Lando PHP container

Not that this matters much, but just for coverage this is my local

I used your Vanilla Drupal 9 recipe in the docs, and although I am on a non-supported version of docker, that doesn't appear to be the cause of issue here as an unsupported php version is being used by your recipe.

Hi, I have tried all the steps by creating a new folder, lando init, lando start, lando pull but the website isn't still working
Error: The website encountered an unexpected error. Please try again later.

I also checked lando info and the database connection also seems to be fine.

Help would be appreciated.

I have installed lando v3.6.2 in Centos version 8. Running drupal 10 recipe.

name: my-first-drupal10-app
recipe: drupal10
config:
  webroot: .

 NAME            my-first-drupal10-app                        
 LOCATION        /home/suresh/projects/drupal10               
 SERVICES        appserver, database                          
 APPSERVER URLS  https://localhost:49282                      
                 http://localhost:49283                       
                 http://my-first-drupal10-app.lndo.site:8000/ 
                 https://my-first-drupal10-app.lndo.site/    

I want to access drupal instance http://localhost:49283 from my server ip address http://170.240.49.45:49283 but I couldn't access it in browser.

How to assign domain name to the http://localhost:49283 instance.

thank you.

I hadn't spun up a local instance recently and was running Lando 3.4.3. Upgraded to 3.6.0, rebuilt the app, destroyed the app, uninstalled lando and docker, reinstalled, tried using a blank default recipe after trimming my customized one down. Running a Drupal 9.3.6 site. Docker Desktop Version 3.6.0 (3.6.0.5487)

The first time I run lando start it runs properly, after that I get a warning that the composer step failed due to autload.php. The local dev site gives me the following message:

Warning: require(/app/vendor/composer/../laminas/laminas-zendframework-bridge/src/autoload.php): failed to open stream: No such file or directory in /app/vendor/composer/autoload_real.php on line 75 Fatal error: require(): Failed opening required '/app/vendor/composer/../laminas/laminas-zendframework-bridge/src/autoload.php' (include_path='/app/vendor/pear/archive_tar:/app/vendor/pear/console_getopt:/app/vendor/pear/pear-core-minimal/src:/app/vendor/pear/pear_exception:.:/usr/local/lib/php') in /app/vendor/composer/autoload_real.php on line 75 

The launchpass link for signing up in slack is also non-functional.

OS: Win 11 Pro 22H2 / WSL2
Lando 3.6.11
Docker version 20.10.23, build 7155243
Docker Desktop 4.17.0 (99724)

Cant run any command with lando. It startet after composer update of drupal, drush and other packages
For lando version, init or start i get below error:

Unhandled rejection TypeError: Cannot read properties of undefined (reading 'split')
at /snapshot/cli/node_modules/@lando/platformsh/lib/config.js
at arrayMap (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at Function.map (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at interceptor (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at Function.thru (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at /snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js
at arrayReduce (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at baseWrapperValue (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at LodashWrapper.wrapperValue (/snapshot/cli/node_modules/@lando/platformsh/node_modules/lodash/lodash.js)
at Object.getSyncableRelationships (/snapshot/cli/node_modules/@lando/platformsh/lib/config.js)
at AsyncEvents. (/snapshot/cli/node_modules/@lando/platformsh/app.js)
at AsyncEvents.handle (/snapshot/cli/node_modules/@lando/core/lib/events.js)
at /snapshot/cli/node_modules/@lando/core/lib/events.js
From previous event:
at AsyncEvents.emit (/snapshot/cli/node_modules/@lando/core/lib/events.js)
at /snapshot/cli/node_modules/@lando/core/lib/app.js
From previous event:
at App.init (/snapshot/cli/node_modules/@lando/core/lib/app.js)
at /snapshot/cli/bin/lando.js
at processImmediate (node:internal/timers:466:21)
From previous event:
at Object. (/snapshot/cli/bin/lando.js)
at Module._compile (pkg/prelude/bootstrap.js:1887:22)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.runMain (pkg/prelude/bootstrap.js:1940:12)
at node:internal/main/run_main_module:17:47

The PHP version and Drush version are touted as configurable in the Drupal plugin doc site:

• Configurable php version from 5.3 all the way to 8.1
• Configurable composer and drush

However, that is not consistent with the code, as values are hardcoded for php and drush in the drupal9 recipe builder (and other recipes appear to also hardcode these values):

Indeed, the following .lando.yml config still installs PHP 8.0:

name: test-project
recipe: drupal9

config:
  php: 8.1

It would be very helpful to make these configurable, as the documentation suggests.

The Drupal console appear to be installed by default on the Drupal 8 recipe; however, it doesn't appear to be installed on the Drupal 9 recipe.

Could you add the Drupal console to the Drupal 9 recipe?

If not, could you document how to make it work on the Drupal 9 recipe?

I'm having trouble configuring the extension=mongodb.so value in the server's php.ini file while setting up the MongoDB service on Drupal. The installation process for everything else is going smoothly.

Here is the content of my .lando.yml file:

name: drupal
recipe: drupal10
config:
  webroot: web
  composer_version: 2.2.16
  via: nginx
  php: 8.1
  database: 'mariadb:10.4'
services:
  myservice:
    type: phpmyadmin
  mongoservice:
    type: mongo
    portforward: true
    creds:
      - mongo
  phpservice:
    type: php
    build_as_root:
      - pecl install mongodb
      - docker-php-ext-enable mongodb
    config:
      php: config/php.ini

And here is the code in the php.ini file:

[PHP]

extension=mongodb.so

I'm receiving the following warnings:

Build process completed successfully Installing '/usr/local/lib/php/extensions/no-debug-non-zts-20190902/mongodb.so' install ok: channel://pecl.php.net/mongodb-1.15.3 configuration option "php_ini" is not set to php.ini location You should add "extension=mongodb.so" to php.ini

Could you please provide any advice or guidance on this issue? Thank you in advance.

Lando version 3.6.0
Docker 4.18.0
on Windows 10
Drupal 7 and Drupal 9

Since 12/5/23, I am unable to get to the EDGE URLS.
This is the message displayed on lando
The service "appserver_nginx" is not running!
This is likely a critical problem and we recommend you run the command below to investigate
lando logs -s appserver_nginx

I see the following error in the containersite-error.log in the .lando folder
{"level":"error","message":"Could not open input file: /tmp/composer-setup.php","label":"compscid9sbu","timestamp":"2022-02-03T19:34:22.580Z"}
{"message":"","stack":"Error\n at /snapshot/cli/lib/shell.js\nFrom previous event:\n at Shell.sh (/snapshot/cli/lib/shell.js)\n at Object.dc (/snapshot/cli/lib/bootstrap.js)\n at compose (/snapshot/cli/lib/bootstrap.js)\nFrom previous event:\n at /snapshot/cli/lib/router.js\n at processImmediate (internal/timers.js:464:21)\nFrom previous event:\n

I tried the following but the error is the same.
lando rebuild / lando destroy lando start / Restarting Docker Desktop etc

Following are the contents of my .lando.yml file for Drupal 9 website
name: compscid9sbu
recipe: pantheon
config:
framework: drupal9
site: compscid9sbu
id:

Add triage/contributor permissions for @AaronFeledy in this repo