Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coerce all manager caches to /tmp/containerbase #2988

Closed
rarkins opened this issue Jul 26, 2024 · 1 comment · Fixed by #3036
Closed

Coerce all manager caches to /tmp/containerbase #2988

rarkins opened this issue Jul 26, 2024 · 1 comment · Fixed by #3036
Assignees
Labels
breaking Breaking change, requires major version bump priority-2-important User-visible bugs or very important features status:in-progress Someone is working on implementation type:feature Feature (new functionality)
Milestone

Comments

@rarkins
Copy link
Member

rarkins commented Jul 26, 2024

We need to support two different read-only FS scenarios:

Full install at build time, no dynamic installs: in this case /opt/containerbase will be fully prepopulated, so cannot be mapped to a Volume, so needs to be read-only after build.

No/minimal install at build time, all dynamic installs: in this case /opt/containerbase should be mapped to a Volume and assumed to be empty at the beginning.

To support the first one in particular, we should coerce all package manager caches to a location in /tmp, proposed: /tmp/containerbase/cache. We should also assume in both scenarios above that either /tmp or /tmp/containerbase is mapped to a Volume and empty to begin with.

Ideally we can coerce all package managers to use our custom cache location through environment variables, and then Renovate does not need to set/override these when calling package managers through child processes.

@rarkins
Copy link
Member Author

rarkins commented Jul 26, 2024

Past issue: #2713

@viceice viceice added breaking Breaking change, requires major version bump priority-2-important User-visible bugs or very important features status:in-progress Someone is working on implementation labels Jul 26, 2024
@viceice viceice added this to the v12 milestone Aug 1, 2024
viceice added a commit that referenced this issue Sep 30, 2024
viceice added a commit that referenced this issue Sep 30, 2024
@viceice viceice added the type:feature Feature (new functionality) label Oct 1, 2024
viceice added a commit that referenced this issue Oct 1, 2024
viceice added a commit that referenced this issue Oct 1, 2024
viceice added a commit that referenced this issue Oct 1, 2024
- Closes #2988

BREAKING CHANGE: `elixir` and `sbt` are now need a prepare step for rootless install.
viceice added a commit that referenced this issue Oct 1, 2024
- Closes #2988

BREAKING CHANGE: `elixir` and `sbt` are now need a prepare step for rootless install.
@viceice viceice closed this as completed Oct 1, 2024
viceice added a commit that referenced this issue Oct 1, 2024
- Closes #2988

BREAKING CHANGE: `elixir` and `sbt` are now need a prepare step for rootless install.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking change, requires major version bump priority-2-important User-visible bugs or very important features status:in-progress Someone is working on implementation type:feature Feature (new functionality)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants