You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm trying run the atlassian jira-software container and I am running into a problem where the container throws the error: "/opt/atlassian/jira/bin/setenv.sh: line 59: ulimit: open files: cannot modify limit: Operation not permitted". This error occurs when using image versions 9.2.1 and 9.7.0. We're using the latest version of the helm chart from https://github.com/atlassian/data-center-helm-charts/releases to launch the images. If I exec into the image before it's able to start and the ulimits are set to 26144. After the image has started, the ulimits are set to 1024 for both root and jira. I looked at /etc/security/limits.conf, but by default it appears all the settings are commented out. Am I missing a helm setting that I need to enable to get this to work?
We were using containerd, not docker for our container execution. There is a config file for containerd (cri-base.json) that is similar to docker's docker.conf. In there, there is a setting named RLIMIT_NOFILE with two children: hard and soft. Those were controlling our ulimits. Once that file was updated and the services were restarted, everything started working as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.