Delivery and Debugging MariaDB Docker Official Images
summary
Maintenance of the MariaDB Docker images surfaces concrete container-only failures: 30 seconds for 12 MB writes on some NFS setups, CFS/setfattr failures, WSL reporting ENOENT after rename on open descriptors, and seccomp blocked clone3 on older runtimes; fixes include skipping unsafe ops on read-only mounts and adding a lock-table for slow timezone initialization so startup finishes. CI now publishes per-commit CI images that users can run to verify fixes, a migration mode runs on a separate port with a migration-volume, and vulnerability scanner false positives (gosu, Go stdlib) drive clearer reporting and tooling in the images.
AI-written summary · about
chapters (20)
- 0:00MariaDB Docker image challenges
- 3:12Container storage performance issues
- 5:21WSL compatibility bugs
- 7:06Failures after base updates
- 9:37Community cooperation and failure
- 10:42False vulnerability reports
- 13:55Security scanner inaccuracies
- 16:02SECCOMP restrictions and limits
- 17:30Runtime differences with Apptainer
- 18:58Startup and shutdown timeouts
- 20:02SystemD integration benefits
- 21:26Writable config vulnerabilities
- 23:35Slow timezone initialization
- 25:25Database migration challenges
- 26:50CI integration opportunities
- 29:00Testing versions in CI pipelines
- 31:11Debugging with pre-release containers
- 33:00Community collaboration and checks
- 35:12Improving security assessments
- 36:39Conclusion and humorous bug reports
related talks
17mState of MariaDB
17mMariaDB Buildbot, the journey of a reinvention
57mBreaking and Fixing your ‘Docker’ ized environments
24mMariaDB post-release quality assurance in Debian and Ubuntu
38mFrom Docker'fail to Dockerfile.. a true story!
20mDrupal Docker and Debugging
06mMariaDB Buildbot Container environments
50mComposing your Containerized Microservices