Randy Fay
Randy Fay
I think that probably this happened when doing the gzipped snapshots and we're not looking for the correct prebuilt gzipped snapshot on startup, so it just doesn't use one.
The problem is here: https://github.com/drud/ddev/blob/04b054319849e57d4ceb297e12c3be24dbf32f59/containers/ddev-dbserver/files/docker-entrypoint.sh#L81-L103 The `db_mariadb_version.txt` file is no longer used with gzipped snapshots, so this stanza doesn't get executed.
AFAICT this was just a build problem, affecting only the 10.3 image. Not sure how that can happen, but I added a test for it. * #3753
I'm seeing this in all mariadb/mysql databases after building new images for v1.19.4 in * https://github.com/drud/ddev/pull/4010 I can't see any relevant changes between v1.19.3 and v1.19.4, and inspection of the...
For the v1.19.4 mariadb/mysql images, when I created them using either of the github workflows, they came out with the wrong default charset. When I pushed all from my arm64...
I think this means you're happy @tyler36 - but the reason this is open is that some image build techniques leave the default broken.
Updated title.
I think the basic way to start exploring this is just to - [x] do a build on linux and see if this happens - [ ] Do a build...
I don't see this happening, closing for now, happy to reopen if we return to this.
Thanks for this great idea. I'm not entirely sure can work across platforms, but definitely worthy!