Skip to content

Remove privileged flag from DB2 container class #4306

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

Closed
wants to merge 1 commit into from

Conversation

rnorth
Copy link
Member

@rnorth rnorth commented Jul 27, 2021

Background:

https://db2indocker.blogspot.com/2015/04/db2-do-not-start-in-un-privileged.html

The main reason behind this is that DB2 needs larger shared memory segments. By default, Linux containers get shared memory segments of 32 MB in Kernel Versions less than 3.16.
In kernel versions 3.16 and above this issue has been addressed and Linux containers get much larger shared memory segments.
That’s why we add —privileged=true parameter when running it.

Kernel 3.15 went EOL in 2014, so this seems like a workaround that shouldn’t be particularly necessary - if it’s just for the reason cited in that blog post.

@kiview
Copy link
Member

kiview commented Oct 14, 2021

If we would update Db2TestImages to ibmcom/db2:11.5.5.1, this will work. I'd be happy if we would include this.

@eddumelendez
Copy link
Member

Done in #9460

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

Successfully merging this pull request may close these issues.

3 participants