You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
I'm getting started with docker and really like your project! I was wondering if you had any way to pass the JVM arguments (or any other argument in /opt/jira/bin/setenv.sh) to the container at start?
I tried to run it as docker run -d --name jira -p 8080:8080 -e JVM_MAXIMUM_MEMORY="2048m" --volumes-from jira_datstore atende/jira but I assume this doesn't work out of the box?
Right now the only way I can think to do it is bake the options into the setenv.sh after building a new docker image and commit the changes post-build, then make a new image.
The text was updated successfully, but these errors were encountered:
I guess the install script should edit the setenv.sh in the bin of jira, to accommodate existing JAVA_OPTS env variable, or provide a way to override the JAVA_OPTS in the file. But I'm commenting without looking :-)
I will check that latter.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey there,
I'm getting started with docker and really like your project! I was wondering if you had any way to pass the JVM arguments (or any other argument in
/opt/jira/bin/setenv.sh
) to the container at start?I tried to run it as
docker run -d --name jira -p 8080:8080 -e JVM_MAXIMUM_MEMORY="2048m" --volumes-from jira_datstore atende/jira
but I assume this doesn't work out of the box?Right now the only way I can think to do it is bake the options into the
setenv.sh
after building a new docker image and commit the changes post-build, then make a new image.The text was updated successfully, but these errors were encountered: