[BUG] TLS Error on Valkey container with valkey-cli about valkey

[hwware]

Did you try with the native Valkey? If yes, is there same issue?

[Nakuromi]

Thanks for you reply.
As I says, I can't try with native install, I have to use a podman container.

So after some time and thought, I'm adding certs & keys in container with --secret option and file type instead of just --volume shared.
And I don't understand why, but it's working...

Even if the volume option is exactly the same result on the disk for file shared, it's working with --secret but not with --volume.
I've configured uid and guid and these were right in both solutions and files were apparently sames.
I'll explore this later in order to understand what is different and why secret option makes this working.
Maybe I've not understand difference in the good way but for me, the --secret option is for security way and not result : file shared with both solution have to be samed.

Strange ^^

After that, the question is also, is it a bug with valkey image for container way or is this normal behavior ?
And if this is normal behavior, maybe add explaination in TLS.md documentation ?

Thanks :)