-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add support for building and testing mariadb-container on RHEL10 #262
Conversation
…r on RHEL10 Signed-off-by: Petr "Stone" Hracek <[email protected]>
Signed-off-by: Petr "Stone" Hracek <[email protected]>
Pull Request validationSuccess🟢 CI - All checks have passed Auto MergeFailed🔴 Pull Request has unsupported target branch Success🟢 Pull Request is not marked as draft and it's not blocked by |
Differences between C10S and RHEL10 are here:
Differences between RHEL9 and RHEL10 are:
|
Local tests PASSED:
|
Let's first shot. [test] |
Testing Farm results
|
Signed-off-by: Petr "Stone" Hracek <[email protected]>
[test] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
10.11/Dockerfile.rhel10
Outdated
rpm -V $INSTALL_PKGS && \ | ||
/usr/libexec/mysqld -V | grep -qe "$MYSQL_VERSION\." && echo "Found VERSION $MYSQL_VERSION" && \ | ||
dnf -y clean all --enablerepo='*' && \ | ||
mkdir -p /var/lib/mysql/data && chown -R mysql.0 /var/lib/mysql && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chown -R mysql.0
Is the user really named mysql.0
, or is it just a typo from mysql
or mysql:0
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's even present in every dockerfile (fedora, centos, rhel) in every version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you can see here. It is present for really long. time. I have google it find in 'coreutils'
https://serverfault.com/questions/194295/using-dot-as-delimiter-to-specify-group-in-chown
Some older scripts may still use '.' in place of the ':' separator. POSIX 1003.1-2001
(see [Standards conformance](http://www.gnu.org/software/coreutils/manual/html_node/Standards-conformance.html))
does not require support for that, but for backward compatibility GNU chown supports '.' so long as no ambiguity results.
New scripts should avoid the use of '.' because it is not portable,
and because it has undesirable results if the entire owner'.'group happens to identify a user whose name contains '.'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some older scripts may still use ‘.’ in place of the ‘:’ separator. POSIX 1003.1-2001 (see Standards conformance) does not require support for that, but for backward compatibility GNU chown supports ‘.’ so long as no ambiguity results, although it issues a warning and support may be removed in future versions. New scripts should avoid the use of ‘.’ because it is not portable, and because it has undesirable results if the entire owner‘.’group happens to identify a user whose name contains ‘.’.
From: https://www.gnu.org/software/coreutils/manual/html_node/chown-invocation.html#chown-invocation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After a discussion let's change it got ':' only for relevant Dockerfiles.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fixed by 41d3ed4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we are at it, I suggest to clear it up a bit more, and use the same data type in the whole expression, so either only integers 27:0
or preferably only strings mysql:root
---- Some older scripts may still use '.' in place of the ':' separator. POSIX 1003.1-2001 (see [Standards conformance](http://www.gnu.org/software/coreutils/manual/html_node/Standards-conformance.html)) does not require support for that, but for backward compatibility GNU chown supports '.' so long as no ambiguity results. New scripts should avoid the use of '.' because it is not portable, and because it has undesirable results if the entire owner'.'group happens to identify a user whose name contains '.'. ---- Signed-off-by: Petr "Stone" Hracek <[email protected]>
Let's test it again after change chown from '.' to ':' [test] |
1) Use common ':' separator instead of unusual '.' one, as disscussed here: sclorg#262 (comment) 2) Use the same data type in the whole expression, so either only integers '27:0' or preferably only strings 'mysql:root' as suggested here: sclorg#262 (comment)
The pull request is separated into two commits.
The first commit adds support for building and testing mariadb-container especially version '10.11' on RHEL10.
The second commit updates README.md file with RHEL10 support.