What the server writes, checked in the code and on the lab's pods (read-only root, after a day of mail, backups, metrics and both upgrade tests: /tmp and /var/lib/inbuxa both empty):
/tmp: application bundles unpack here (std::env::temp_dir()), unless an Application sets unpackDirectory.
the working directory (/var/lib/inbuxa in the image): migrations' work files under migrations/ (or $INBUXA_MIGRATIONS_DIR).
RocksDB/filesystem store snapshots: under the store's own path; not used with PostgreSQL.
config.json: only bootstrap and saving the data store settings write it.
That last one is the only thing a read-only setup gets wrong: on Kubernetes config.json is a read-only mount of server.dataStore, and a save through the API failed the whole request with the I/O error. Now the registry checks the file can be written first; when it can't (read-only or not permitted) that object is refused with forbidden and:
The data store settings are in config.json, which this server can't write: it's managed outside the server (on Kubernetes, the chart's server.dataStore value). Change them there.
Other write errors fail as before, now with the path in the event.
cargo check -p store -p jmap clean (no new warnings), unit test for the read-only check, fmt, fork checks. The chart side (documenting the paths) is a separate charts PR.
Part of #428 (K-S5, read-only root).
What the server writes, checked in the code and on the lab's pods (read-only root, after a day of mail, backups, metrics and both upgrade tests: `/tmp` and `/var/lib/inbuxa` both empty):
- `/tmp`: application bundles unpack here (`std::env::temp_dir()`), unless an Application sets `unpackDirectory`.
- the working directory (`/var/lib/inbuxa` in the image): migrations' work files under `migrations/` (or `$INBUXA_MIGRATIONS_DIR`).
- RocksDB/filesystem store snapshots: under the store's own path; not used with PostgreSQL.
- `config.json`: only bootstrap and **saving the data store settings** write it.
That last one is the only thing a read-only setup gets wrong: on Kubernetes `config.json` is a read-only mount of `server.dataStore`, and a save through the API failed the whole request with the I/O error. Now the registry checks the file can be written first; when it can't (read-only or not permitted) that object is refused with `forbidden` and:
> The data store settings are in config.json, which this server can't write: it's managed outside the server (on Kubernetes, the chart's server.dataStore value). Change them there.
Other write errors fail as before, now with the path in the event.
`cargo check -p store -p jmap` clean (no new warnings), unit test for the read-only check, fmt, fork checks. The chart side (documenting the paths) is a separate charts PR.
On Kubernetes config.json is a read-only mount of the chart's
server.dataStore. Saving the data store settings through the API then
failed the whole request with the write error. The registry now checks
the file can be written first and, when it can't (read-only or not
permitted), refuses that object with forbidden and a description saying
the settings are managed outside the server and where to change them.
Other write errors still fail as before, with the file's path.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #428 (K-S5, read-only root).
What the server writes, checked in the code and on the lab's pods (read-only root, after a day of mail, backups, metrics and both upgrade tests:
/tmpand/var/lib/inbuxaboth empty):/tmp: application bundles unpack here (std::env::temp_dir()), unless an Application setsunpackDirectory./var/lib/inbuxain the image): migrations' work files undermigrations/(or$INBUXA_MIGRATIONS_DIR).config.json: only bootstrap and saving the data store settings write it.That last one is the only thing a read-only setup gets wrong: on Kubernetes
config.jsonis a read-only mount ofserver.dataStore, and a save through the API failed the whole request with the I/O error. Now the registry checks the file can be written first; when it can't (read-only or not permitted) that object is refused withforbiddenand:Other write errors fail as before, now with the path in the event.
cargo check -p store -p jmapclean (no new warnings), unit test for the read-only check, fmt, fork checks. The chart side (documenting the paths) is a separate charts PR.