Avoid new log file when new instance of container with number
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose
- Domain
- devops, observability-sre
Research direction
The issue names no files, tests, or entry points; start by searching the repository for the logic that derives log filenames from container names and inspect any related tests. Done means defining behavior that keeps one log across docker-compose scale-out and scale-in while preserving logs for the active container.
Written by the indexing model from the issue text.
Description
We deploy new releases in a new container with docker-compose --scale (out -> test -> in).
Then it creates a new container with a number in the name, like app_api_13 and next deploy scale out to app_api_14, and delete old app_api_13 at scale in ..... the log file follow the new containers name after each deploy, then we have lot of log files:
app_api_10.log app_api_11.log app_api_12.log app_api_13.log app_api_14.log app_api_9.log
when just last log app_api_14.log is the container running.
Is there are way to avoid number in log and maintain just one log, avoid number?
- Dominant language
- Go
- Stars
- 255
- Forks
- 37
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from umputun/docker-logger
-
Difficulty 5/5 Over a week Newbie friendliness 48/100
umputun/docker-logger#64 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
umputun/docker-logger#24 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
umputun/docker-logger#16 ·
All issues in umputun/docker-logger
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100