Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Caching is too agressive

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, shell

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.

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

Dominant language
Shell
Stars
0
Forks
1
Avg merge
1d 5h
Merged PRs (30d)
5

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenConext/OpenConext-BaseContainers

All issues in OpenConext/OpenConext-BaseContainers

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.