search

10up / wp-local-docker-v2

ARCHIVED: A simple Docker based development environment for WordPress.
MIT License
484 stars 81 forks source link

Startup hangs on Waiting for MariaDB for v3.0.0 #272

Open tcmulder opened 2 years ago

tcmulder commented 2 years ago

Describe the bug After upgrading to 3.0.0 I'm unable to start MariaDB: the command line simply says "Waiting for MariaDB", and the logs in Docker Desktop start erroring (details below).

I've been able to get around this by downgrading .wplocaldocker/global/docker-compose.yml from image: mariadb:10.3 to the previous image: mariadb. Docker flags that as being amd64 (I'm on an M1), but at least it runs.

I read in a thread somewhere that this might be caused by Docker previously using mysql and now using mariadb, so I'm not sure if the upgrade to 3.0.0 caused any issues. The site I'm currently working on has always been on 3.0.0 though, and prevous sites were using the older version of mariadb as well.

Note I've also run 10updocker configure to ensure no customizations existed (although now as I mentioned I've manually downgraded mariadb). I also tried restarting my computer and still no luck.

EDIT: note I've now been able to get it working by changing image: mariadb:10.3 to image: mariadb:latest, so perhaps it's something that mariadb has fixed in a more recent version.

Steps to Reproduce

  1. Upgrade to 3.0.0.
  2. Run 10updocker start for any site.
  3. At this point, the global image won't start up as it will hang on "Waiting for MariaDB"

Expected behavior The global image should start up, after which the site's image can start up normally.

Environment information

Additional context Here's the full log:

2021-12-28 14:18:39+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.3.32+maria~focal started.

2021-12-28 14:18:40+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'

2021-12-28 14:18:40+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.3.32+maria~focal started.

2021-12-28 14:18:40 0 [Note] mysqld (mysqld 10.3.32-MariaDB-1:10.3.32+maria~focal) starting as process 1 ...

2021-12-28 14:18:40 0 [Note] InnoDB: Using Linux native AIO

2021-12-28 14:18:40 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2021-12-28 14:18:40 0 [Note] InnoDB: Uses event mutexes

2021-12-28 14:18:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2021-12-28 14:18:40 0 [Note] InnoDB: Number of pools: 1

2021-12-28 14:18:40 0 [Note] InnoDB: Using generic crc32 instructions

2021-12-28 14:18:40 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M

2021-12-28 14:18:40 0 [Note] InnoDB: Completed initialization of buffer pool

2021-12-28 14:18:40 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2021-12-28 14:18:40 0 [ERROR] InnoDB: Invalid flags 0x15 in ./ibdata1

2021-12-28 14:18:40 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption

2021-12-28 14:18:40 0 [Note] InnoDB: Starting shutdown...

2021-12-28 14:18:40 0 [ERROR] Plugin 'InnoDB' init function returned error.

2021-12-28 14:18:40 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2021-12-28 14:18:40 0 [Note] Plugin 'FEEDBACK' is disabled.

2021-12-28 14:18:40 0 [ERROR] Unknown/unsupported storage engine: InnoDB

2021-12-28 14:18:40 0 [ERROR] Aborting
benlk commented 1 year ago

I'm having this issue on 4.0.0-rc.3. My issue was just a disk out of space errror.

benlk commented 9 months ago

Two ways this out-of-disk error can occur, and their solutions: