Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY #79

Open
eampudia opened this issue Sep 7, 2018 · 3 comments
Open

Configure JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY #79

eampudia opened this issue Sep 7, 2018 · 3 comments

Comments

@eampudia
Copy link

eampudia commented Sep 7, 2018

Dear Martin,
Thanks for your contribution to the docker community, it will be nice to be able to changes the values of the memory to run Jira adding some docker variables.

Thanks,

Emilio

@0rph3us
Copy link

0rph3us commented Sep 28, 2018

I have a small fix for this problem in my own Dockerfile

FROM cptactionhank/atlassian-jira:7.12.2

USER root:root

ENV JVM_MAXIMUM_MEMORY 768m
ENV JVM_MINIMUM_MEMORY 384m

# make memory 
RUN set -x \
    && sed --in-place 's/JVM_MINIMUM_MEMORY=.*/#JVM_MINIMUM_MEMORY=/g' /opt/atlassian/jira/bin/setenv.sh \
    && sed --in-place 's/JVM_MAXIMUM_MEMORY=.*/#JVM_MAXIMUM_MEMORY=/g' /opt/atlassian/jira/bin/setenv.sh

# change user
USER daemon:daemon

@bradjones1
Copy link

An option would also be to mount your own setenv.sh on top of the existing one, at runtime. You can mount a specific item in a config map in K8s, per this SO answer.

@riav
Copy link

riav commented Jun 19, 2019

It is possible to change the memory parameters, among others, through the variable JAVA_OPTS

JAVA_OPTS: "-Xms4g -Xmx4g"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants