#5.7.6 mysql delete user full
Remove deploy scripts to avoid full path disclosureĬommit 422173838743e44118b1c5b0c9bd023f1ae94aaf XDEBUG_CONFIG: "remote_host= idekey=IDE_XDEBUG"īLACKFIRE_CLIENT_ID: $Ĭlearing the project's history in order to opensource it without any potential sensitiveĬommit 2b09a138f01623f39a2938e459a47b21f3e79dad # If you develop on Linux change this to remote_host=172.17.0.1 # If you develop on Windows change this to remote_host= # If you develop on Linux, comment out the following volumes to just use bind-mounted project directory from host # Comment out these volumes in production Adjusting the default configuration of the image is something we'd defer to a decision by upstream.Īdditionally, "no reaction" is a bit of an overstatement - all three co-maintainers of this image have chimed in more than once on the exact issue you're commenting on. If all we do is delete the lost+found directory when it exists, then it might return (as it's a feature of the underlying filesystem, not userspace). If I recall correctly, the way storage is configured for Pods in Kubernetes even makes using a subdirectory of the mounted volume really trivial. without having to deal with doing that at the full partition level. Honestly, I would always recommend that for any service, one should be providing a subdirectory of the formatted partition rather than the root of it (not just for MySQL deployments, but across the board) - it adds a lot of benefits beyond just avoiding "the lost+found problem", including and especially the flexibility to move the directory around, snapshot it, etc.
0 kommentar(er)
