stackabletech / stackabletech/docker-images
Rework: Docker images according to best practice
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
-
Split generic COPY stackable/ into subdirectories and copy those only in layers necessary
Currently we do things like that:COPY --chown=stackable:stackable hive/stackable /stackableWe want to be a bit more precise with that.
-
We need to take care about when to create which layer in terms of what is changing often in the end, less changing in the Beginning
We should reduce build times and avoid changing layers to often.
This will have the advantage of reducing buildtimes and only change layers when the change is really in there.
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.
Research direction
Start by inventorying the repository's Dockerfiles and the current generic COPY stackable/ usage, including the hive/stackable example. Review the existing image build order and identify which content changes most often. Done means relevant directories are copied only where needed, layers are ordered to reduce unnecessary rebuilds, and image builds remain successful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100