doc: mysql permissions error and mitigation #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running into a deployment issue, I wanted to document the mitigation.
The TL;DR is: mitigate before
docker-compose up
using:chmod -R ugo+rx env/mysql
Of note: my docker-compose is a
1.28
whereas the most recent commit(s) have upgraded for a docker-compose2.7
. That may be the source of my issue, and if so, I'd prefer to still document it for others in case it's related to an evolvingmariadb
container.