docker / docker/docker-credential-helpers
java util FileHandler INFO/DEBUG logs printing as STDERR
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 195
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
We have implemented simple spring boot application with java.util.logging, when we start application with docker run -p 8080:8080 -t springio/gs-spring-boot-docker
everything showing as "stdout", where as if we remove option "-t" and re-run then it is able to print "System.err.println" as STDERR and remaining all are in stdout.
Posted similar question in stackoverflow : https://stackoverflow.com/questions/60393953/docker-json-logging-driver-spring-boot-application
I understand this might be process to create issue, or this may be related to forums. but still want to know answer. Can anybody help us how to instruct docker to distinguish b/w stdout and stderr ?
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
No repository files, tests, or entry points are identified; the issue describes a Spring Boot application using java.util.logging and Docker output behavior. Start with the linked Stack Overflow question and the reported difference between running with and without -t. Done would require a reproducible, repository-relevant diagnosis, but the payload does not define a change to make.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, spring-boot
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100