OSTREE-ADMIN-UNLOCK(1)
β¨ NAME β¨
okay so this is the OSTree manual page for ostree-admin-unlock, and it's all about prepping your current deployment for a hotfix or some development time. π
πΈ SYNOPSIS πΈ
ostree admin unlock [OPTIONS...]
π DESCRIPTION π
So here's the vibe, bestie: this removes the read-only bind mount on /usr and replaces it with a writable overlay filesystem. The default unlock invocation is intended for development/testing purposes. All changes in the overlay are lost on reboot π.
But plot twist: this command also supports "hotfixes" β see below. π
π OPTIONS π
--hotfixβ if you pass this, the current deployment will be cloned as a rollback target. This option is for things like emergency security updates to userspace components such assshd. The semantics here differ from the default "development" unlock mode in that reboots will retain any changes, which is what you likely want for security hotfixes. π₯--transientβ if you pass this, the overlay filesystem will be mounted read-only. It can still be affected by remounting it as read/write in a new mount namespace. For example:
ostree admin unlock --transient
unshare -m -- sh -c 'mount --options-source=disable -o remount,rw /usr && touch /usr/myfile'
okay that's a wrap, bestie β source/version: the OSTree manual, page OSTREE ADMIN UNLOCK(1), and the date? it's not printed on this footer, so no invented date energy here π
π¦ where this page comes from
- arch rolling: ostree 2026.6-1 Β· LGPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms