OpenConext / OpenConext/OpenConext-BaseContainers
Caching is too agressive
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
The caching works so well that it hardly ever runs a new apt-get upgrade.
Not sure if that's a problem, because it does pick up changes in the upstream images
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 inspecting the Docker base-image build configuration and how its cache affects apt-get upgrade. The issue does not name files or tests, so first clarify the intended refresh or invalidation behavior; done means agreeing on that behavior and verifying that upstream image changes and package upgrades are picked up as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100