Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,266
Community Members
 
Community Events
176
Community Groups

How to add TLS certificate to crowd running container

Running crowd application (v4.0) in kubernetes container using docker crowd image. Need TLS certificates to be installed and tomcat/server.xml to be updated in run time. Tried to map certificate and tomcat/server.xml file to shared volume, When pod spin up the shared volume data is getting overwriten. Tried to use execute command/args to image but after executing the command pod is exited (seems the command is overwritting the entrypoint command inside the pod.

Is there any solution where certificates and server.xml can be updated in runtime and then start crowd.sh

1 answer

0 votes
Dave Chevell Atlassian Team Jun 02, 2020

Hey @saint 

tl;dr mount your custom server.xml to /opt/atlassian/etc/server.xml.j2

As per the note under the "Advanced Configuration" section of https://hub.docker.com/r/atlassian/crowd , server.xml and other config files tied to the installation folder are generated from Jinja2 templates. You noticed that server.xml is overwritten on startup; they're overwritten using the template located at /opt/atlassian/etc/server.xml.j2

Whilst our built-in template contains a number of merge fields that are resolved at startup, if you place a static file at this location it will simply be used as-is. 

That should sort out your problem! Let me know how you go :)

Cheers

Dave

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events