It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

To:
CC:

Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.

I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.

If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.

This message will be added only once per issue, regardless of how many times
the Summary is edited.

message-code:summary-edited

, could you please update documentation regarding non-root user?

Hi @mykola.marzhan,

First, thanks for the update.

I am fully aware of the best practices and in fact fully encourage them.

The issue I was facing is that GitHub image library/percona has been deprecated in favor of upstream percona/percona-server.

Because of that I was lead to believe that it would be backwards compatible since it continued to use official docker library repository 'percona' instead of fully deprecating it in favor of 'percona/percona-server'.

In my opinion the best thing would be to either mention this to existing users on library/percona Dockerhub page or completely deprecate the library and instructing users to use percona/percona-server instead.

Regarding tags I do use exact versions for production images, the reason for latest tag is just for testing purposes.

Thanks again and best regards,
Vladimir

,

you can find plenty of best practices and recommendations on the internet about non-root user inside a container. It is a huge anti-pattern to have root user inside a container.
So, without root, we cannot change owner for dir on your host system which mounted into container.

about tags:
in fact 5.7 it is the same to 5.7-latest (if any doubt please read DockerHub guidelines here.
it is a huge amount of articles on the internet - why it is not recommended to use latest tag. Don't ignore them.
if you need assume that nothing should break, please use tags with exact versions, like 5.7.23-stretch or percona/percona-server:5.7.22