Open mencl-elastic opened 1 month ago
Thanks for opening this issue. This is not supported at the moment. As workaround you would need to provide a plaintext private key, or use a reverse proxy that has support for this in front of the package registry.
Trying to get an EPR container deployment running in running in docker/podman using SSL/TLS using an encrypted private key. I know the air gapped documentation at https://www.elastic.co/guide/en/fleet/current/air-gapped.html shows how to do it with plaintext private key, but have not found anything for an encrypted key.
Running podman as shown results in the container starting, but then reporting:
{"log.level":"fatal","@timestamp":"2024-09-12T19:46:40.915Z","log.origin":{"function":"main.main.func1","file.name":"package-registry/main.go","file.line":162},"message":"error occurred while serving","error":{"message":"tls: failed to parse private key"},"ecs.version":"1.6.0"}
If I replace the key with a plaintext private key, the same docker/podman run executes as expected. Is there an environment variable to send the encryption key to EPR so the key may be decrypted and used as intended? EPR_TLS_KEY_PASSPHRASE??