testcontainers / testcontainers/testcontainers-java
Allow logging level to be specified during container creation.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
I'm currently trying to debug an issue where I can run a postgresql container via the command line and I see that the database starts just fine. But testcontainers throws an IllegalArgumentException -> ContainerLaunchException (apparently it thinksthat the PostgreSQLContainer doesn't start properly). I see in the source code that logging is hard-coded to be turned off during the startup process. It would be nice to have a method of changing this value since the information provided is not very useful for debugging.
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
Start at the PostgreSQLContainer startup path and trace where logging is disabled during container creation. Identify the existing hard-coded setting and the container-creation entry point, then make the logging level configurable and verify that startup diagnostics can be enabled when launch fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, postgresql
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100