Skip to content
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

MDBF-568 Fix 11.x missing mysql symlinks #514

Closed
wants to merge 1 commit into from

Conversation

LinuxJedi
Copy link

During apt --no-install-recommends is used which means the -compat packages, which contain the symlinks for mysql command line tools, was not installed for 11.x.

This patch explicitly adds them back.

During apt `--no-install-recommends` is used which means the `-compat`
packages, which contain the symlinks for mysql command line tools, was
not installed for 11.x.

This patch explicitly adds them back.
@fauust
Copy link
Contributor

fauust commented Jun 12, 2023

LGTM, @grooverdan can you merge and create PR on docker's official repo if it's OK for you?

@martadinata666
Copy link

martadinata666 commented Jun 13, 2023

Just a thought doesn't this defeat the purpose of https://jira.mariadb.org/browse/MDEV-30201 ? One thing that may do is to create some announcement to entrypoint that mysqld should be replaced by mariadbd, rather than keeping compat packages. 💭

@LinuxJedi
Copy link
Author

Just a thought doesn't this defeat the purpose of https://jira.mariadb.org/browse/MDEV-30201 ? One thing that may do is to create some announcement to entrypoint that mysqld should be replaced by mariadbd, rather than keeping compat packages. thought_balloon

The answer is a bit more nuanced than that. The original intention was to deprecate with warnings in 11.0 and make it a "recommends" package for RPM/DEB so that for many it was still installed by default. We didn't intend for the consequences of that to be that it was removed from the Docker image.

All that being said, the one instance we know of where it has affected someone, it was due their custom healthcheck code which could have been implemented a little better. We have provided them with a way to do this correctly in their CI.

So, although this was not intentional to do it here and now, this is likely the perfect time and place to do it. Unless we get feedback with a use-case where this is needed, this PR will be closed and we will make sure this is documented.

@martadinata666
Copy link

I see, i thought docker image mariadb:11, intentional removing of compat thing to introduce transition mysqld to mariaddbd, followed by repository that had compat installed, and lead to compat removal. 👍🏼

@grooverdan
Copy link
Member

10.6+ container images already use the native mariadb names. So the compat is explicitly in the user generated extension domain.

@LinuxJedi
Copy link
Author

Unlikely we will do this, blog post given reasoning.

@LinuxJedi LinuxJedi closed this Jun 15, 2023
@fauust
Copy link
Contributor

fauust commented Jun 16, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants