testcontainers / testcontainers/testcontainers-java
DB2 privileged mode is no longer required and should be removed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Currently our DB2Container class uses privileged mode; I think on the basis of this blog post: https://db2indocker.blogspot.com/2015/04/db2-do-not-start-in-un-privileged.html
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.
I would suggest that we remove the requirement for privileged mode for the DB2 container, which would mean that none of our modules use privileged mode at all any more. This is ~ better for everybody's security.
Users would still be able to turn on privileged mode for the DB2 container if their kernel made it essential, but I think this is unlikely.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The DB2Container class is the entry point; start by locating its privileged-mode configuration. Verify that the DB2 container starts without privileged mode and that users can still enable it when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- database, security, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100