• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Docker Environment Variables

paulr

New Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.51_build1800230310.09 os_Ubuntu 22.04
I'm running Docker and need to pass RSA_PRIVATE_KEY as an env variable containing the full text of a PEM formatted private key.

Entering it in the web interface the newlines are escaped (\\n) and I can't find a way to pass the variaable in a way that is acceptable to the container.

I can't find where plesk stores the config for containers (edits to /var/lib/docker/containers/xxx/config.v2.json don't persist). Does anyone know where plesk stores the config for containers? Can I pass the variable in any other way?

Thanks for any pointers.
 
I would also like to know this. But given the degree of responses here from Plesk or other users it appears that this is hard to get. I believe they are stored as .env files. But where they are is a bit of a mystery so far.
 
What docker is this?

Have you tried the CLI?

docker run -d -v /path/to/private-key.pem:/app/private-key.pem -e PRIVATE_KEY_FILE=/app/private-key.pem your_image
 
Back
Top