slimtoolkit / slimtoolkit/slim
Slimify based on multiple commands?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Scenario
I have a single image that is deployed in 3 different ways:
- Running migrations of the app
- Deploy app1 internally on port
5000 - Deploy app2 externally on port
3000
In each case there's some overlap between files used but not all are used. Running docker-slim against (2) ends up removing files used by case (1) and (3) for example.
How can I solve this? Alternatively is there a way to skip specific files?
I'd prefer to not split into 3 separate containers, since everything is tightly coupled and that will introduce a lot of unnecessary maintenace.
Specifications
- Version: linux|Transformer|1.39.1|537c77323f2e9a3d6771aa0ea73a047017774d16|2022-11-13_03:27:40AM
- Platform: Ubuntu 20.04.6 LTS
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 by reviewing how docker-slim processes the single deployment command described in the issue. Compare the three migration and deployment scenarios, then determine how completion should preserve files needed by all commands or support explicitly skipped files. Done means one image can be slimmed for all three uses without removing required files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100