Add SSL Certificate in Docker


I installed Lucee via Docker. All is working find but I’d like to add a SSL certificate for my intranet (provided via our PKI).

How can I generate the CSR request to provide to the PKI ?

Many thanks for your help.


you can either

  1. use SSLCertificateInstall() :: Lucee Documentation
  2. overwrite the the cacerts file under \lucee-server\context\security with your own updated caerts (with you custom root imported)

Lucee 6.0 by default will use the jvm, cacerts file


Thanks for your quick answer :grinning: For the moment, Lucee is installed.

This one was configured via Portainer but in the “volumes”, I only mapped the webroot folder :grinning:

Do I need to mount another volume? Maybe I missed something when I created the container?

did you have a look at the docs?

Of course, I read the doc to be able to use Docker but I have to confess that I didn’t understand which volumes I had to “bind” to the container, the doc is a bit fuzzy for me.

That’s why I’m asking these questions that probably seem obvious to you … :frowning:

ok, next time then cite the bit of the doc which is confusing, so we have 1) context and 2) can improve the docs

that webroot looks wrong to me, as per GitHub - lucee/lucee-dockerfiles: Official Lucee Dockerfiles for Docker Hub build images

Folder locations

Web root for default site: /var/www

To be honest, it was a bit complicated to install Lucee for me. Usually, with an example of a docker-compose, for me, it is easier to understand.

It is clear that I am not an expert in Docker, unfortunately :frowning:

I created my container following this video, maybe isn’t a good idea ? I’m lost between the different explainations and links.

git clone
cd lucee-docker/
docker image build . -t lucee-539 --build-arg LUCEE_VERSION= --build-arg LUCEE_ADMIN_PASSWORD='******' --build-arg LUCEE_EXTENSIONS="6E2CB28F-98FB-4B51-B6BE6C64ADF35473" --build-arg LUCEE_EXTENSIONS="D46B46A9-A0E3-44E1-D972A04AC3A8DC10" --build-arg LUCEE_EXTENSIONS="8D7FB0DF-08BB-1589-FE3975678F07DB17" --build-arg LUCEE_EXTENSIONS="87FE44E5-179C-43A3-A87B3D38BEF4652E" --build-arg LUCEE_EXTENSIONS="FAD67145-E3AE-30F8-1C11A6CCF544F0B7" --build-arg LUCEE_EXTENSIONS="1A1FA05C-CF89-4834-9BC71D617046A6A8" --build-arg LUCEE_EXTENSIONS="B737ABC4-D43F-4D91-8E8E973E37C40D1B" --build-arg LUCEE_EXTENSIONS="A03F4335-BDEF-44DE-946FB16C47802F96" --build-arg LUCEE_EXTENSIONS="2BCD080F-4E1E-48F5-BEFE794232A21AF6" --build-arg LUCEE_EXTENSIONS="1C9A7C34-2555-4AAA-92FBB7FC7111140C" --build-arg LUCEE_EXTENSIONS="CED6227E-0F49-6367-A68D21AACA6B07E8" --build-arg LUCEE_EXTENSIONS="99A4EF8D-F2FD-40C8-8FB8C2E67A4EEEB6" --build-arg LUCEE_EXTENSIONS="7E673D15-D87C-41A6-8B5F1956528C605F" --build-arg LUCEE_EXTENSIONS="66E312DD-D083-27C0-64189D16753FD6F0" --build-arg LUCEE_EXTENSIONS="60772C12-F179-D555-8E2CD2B4F7428718"
docker container run -p 8080:8080 --name lucee-8080 lucee-539

As I understand, it’s not the good solution …