Repository navigation
/.cache not writeable when using PVC as developement area #1108
Description
Due to helm best practices of setting root filesystem as read only, cannot install pre-commit tools into a container when using the PVC as a development area. We could mount this area, when in either debug or with PVC mounted scratch. Or we can disable read-only filesystem again.
Acceptance Criteria
- Specific criteria that will be used to judge if the issue is fixed
Activity
callumforrester commentedon Jul 7, 2025
The other thought I had was to have a separate container for development, rather than try to sequeeze dev and prod environments into the same box
DiamondJoseph commentedon Jul 7, 2025
I'm actually not sure what was causing issues seen on b01-1- as discussed in #1096 that change never actually got added to the default Helm chart.
chore: Update to copier template 5.0.0 and uv (#1290)
chore: Update to copier template 5.0.0 and uv (#1290)
abbiemery commentedon Feb 25, 2026
@dan-fernandes, is this fixed now with the cache location changes?
dan-fernandes commentedon Mar 2, 2026
I'm struggling to work out the exact issue here, and how / whether it's been fixed.
From #1290 it looks like the virtual environment is now stored under
/app/.venvwhich is--chown 1000(default userubuntu). I think this resolves part of the issue.The UV cache is also moved from
.cacheto a writeable directory through #1308, meaning that the root filesystem being non-writeable shouldn't be an issue.When I run
uv add pre-commitin the P49 BlueAPI withdebug: true, it installs successfully. As this seems like the goal, I am going to close the ticket.