gliderlabs / gliderlabs/logspout
High Memory Usage/Memory not freed
- Dominant language
- Go
- Stars
- 4.7k
- Forks
- 661
- PR merge metrics
- No merged PRs in 30d
Description
I'm running many instances of the container on many hosts, but on some hosts the memory begins to grow without being freed. Are there any recommendations to resolve this? Thanks!
100% on the graph is 128mb

docker inspect image:
```
"Id": "sha256:6c7afda380b21c90161d54a1f6d407f17d015efc9fc0b7b8cab7c3fdb6d96513",
"RepoTags": [
"gliderlabs/logspout:latest"
],
"RepoDigests": [],
"Parent": "",
"Comment": "",
"Created": "2016-05-23T21:36:58.770911598Z",
"Container": "79e44e12ada6373446e23ed6dec4e807533339c3346c2035baa2c37f0053ac75",
```
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is named. Start by reproducing the memory growth with many logspout containers across hosts, using the supplied memory graph and Docker image details, then identify where memory remains allocated and define a regression check showing that usage is released.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100