Repository navigation
Issues with Renovate CE in a read-only environment #901
Unanswered
coderanger
asked this question in
Q&A
Replies: 1 comment 2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've already done the debugging but wanted to post something for others who run into the same issue:
I'm running Renovate CE 15.1.0 in Kubernetes and for security I enabled readOnlyRootFileSystem mode. This works fine if you're using the
-fullairgap images but we're trying out switching toinstallmode using Containerbase. This produced a lot of weird error messages that I'll post here for SEO:To trace through the problem: Containerbase uses NeDB to store some metadata information about packages it knows how to install. These files live in
/opt/containerbase/datain the container images. When NeDB loads a database file it reads everything into an in-memory data structure and then it writes the data back to the file system to (potentially) compact things and make sure the database files are in the latest format. This does not appear to be optional, even though Containerbase is treating these databases as read-only (it stores all mutable state undercontainerbaseDirwhich defaults to/tmp/renovate/containerbasewhich is easy to mount on a writable volume) NeDB still requires the files be writable.Given this is a core behavior of NeDB, I don't think there is anything the Renovate team can do about this. For any users who end up here, you can either disable read only mode or do some tricks with initContainers and copying things to a shared emptyDir volume.
All reactions