Support configuring container resource limits
Open
enhancement
- Dominant language
- Go
- Stars
- 189
- Forks
- 24
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 18
Description
Both Podman and Docker support setting resource (memory and CPU usage) limits for containers. We can make these (optionally) user configurable to allow users to test their containers with the same settings they would in production.
From https://github.com/dotnet/aspire/issues/8735
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing how the DCP API server and CLI configure containers for Docker and Podman, then identify where optional CPU and memory settings can be passed through. Done means users can configure both resource limits and container launches honor them for both runtimes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100