-
Notifications
You must be signed in to change notification settings - Fork 444
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
Specify mysql
as container user
#598
Conversation
mysql
as container user
b7f620c
to
518a2fd
Compare
Can't really: https://mariadb.com/kb/en/docker-official-image-frequently-asked-questions/#why-does-the-mariadb-container-start-as-root See #461 Certification provides the option "Indicate that the container requires privileged host-level access in the certification project settings. This setting is subject to Red Hat review." While k8s provides init containers, the base container as a singleton can't. Note: "Red Hat" - always two words. |
@mmontes11 is right, named volumes get permissions of A reworking of the test from #461 (which failed due to a second mounting problem fixed in v5.1.0):
|
That would be ideal, yes, but it might not be a trivial refactor. The |
That might work for podman, but doesn't work for Docker: $ docker run -it --rm --user 1000:1000 --volume foo:/foo bash ls -ld /foo
drwxr-xr-x 2 root root 4096 Jul 9 18:37 /foo |
You could set |
merged c52e778. |
Explicitly declare
mysql
as the container user to be compliant with RedHat container certification :RunAsNonRoot
requirement)Without this, the certifications tests fail:
But it can easily fixed by adding
USER mysql
: