docker-library / docker-library/mysql
Initialisation script errors aren't logged
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.6k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if this is intended behaviour but I was running into a problem of not having all my scripts run and wasn't certain why until I tried to execute the sql in the last script it logs that it's initialising and found a bug someone had introduced. Is it not possible for the container to at least show there was an error with the script or better yet log the actual error to track down the error more easily?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem with a container initialization sequence in which one SQL script fails and a later script is not run. Start by tracing how initialization scripts are executed and how their output is handled. Done means a failing script is visibly reported and its error is available for troubleshooting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mysql, shell
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100