-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
11.5.2 Entrypoint triggered multiple times #605
Comments
The primary cause appears to be:
The volume mount of path leave it to the container to resolve the permissions. Despite the container started as root, where it should try to chown the container datadir to user I can't see a reason for 3 restarts. (or special ib_buffer_pool handling). |
Indeed, removing Logs without the option for reference:
Logs from 11.4.3 with no-new-priviileges:
|
Hm, that's interesting, I went back to 11.5.2 after getting above logs from 11.4.3 on my test environment and... the issue is gone on the rebuilt container 🤔 |
Changing ownership was made non-fatal - docker-library/official-images#17344 Healthcheck also slightly reworked (but don't think that plays a part here). |
but I tried updating after that release was merged, so not sure. also not sure what change of ownership would be at play here, too. |
hm, I upgraded PROD and no issue there, but on test it returned once more. I wonder if this is somehow related to my test host being Windows |
Ack, sorry I can't test all host environments. They, by the goals of containers, should result in something identical. |
I am not saying you should 😅 My job here is small - report something abnormal I've noticed and all relevant information that may help solve it, if at all possible. It does not seem to be affecting actual data or the server as a whole, once it's running, so I'd say this is a low priority thing, too. |
It looks like 11.5.2-noble starts entrypoint 3 times at once. Here's what I have in docker logs:
And here's what I have in my log file
My dockercompose service
My dockerfile
This behavior is not observed on 11.4.3-noble. Number of repeats seem to vary, too: sometimes it's 2, sometimes it's 3. It is possible that container is actually crashing (because MariaDB fails to start), but it's a bit unclear.
The text was updated successfully, but these errors were encountered: