From fb5c4690bf76fcde8840e1f2e10495896b407b1d Mon Sep 17 00:00:00 2001 From: yo Date: Sun, 22 Sep 2024 19:32:07 +0200 Subject: [PATCH] Update README --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5a9ba6c..149d543 100644 --- a/README.md +++ b/README.md @@ -144,7 +144,7 @@ To update jail patch version, use gocage update : Update basejails/releases ---------- -To update basejails, you need to update the release they are base on. Specify release with -r, and the datastore storing concerned release with -d : +To update basejails, you need to update the release they are based on. Specify release with -r, and the datastore storing concerned release with -d : `gocage update -d fastgocage -r 14.1-RELEASE` Upgrade jails @@ -160,11 +160,13 @@ Upgrading basejails currently needs to be done manually, for each jail. The idea is to stop the jail, change the content of its fstab file to point to the new release, then start jail. If one change the fstab while the jail is running, its system directories won't be unmounted at stop time and this will provoke stop errors. To minimize downtime, the change could be scripted: -`gocage stop jail1 + +gocage stop jail1 sed -i .bak 's/14.0-RELEASE/14.1-RELEASE/' /iocage/jails/jail1/fstab # Avoid race-condition by waiting for the update in fstab until grep -q 14.1-RELEASE /iocage/jails/jail1/fstab; do sleep 0.2; done -gocage start jail1` +gocage start jail1 + You can now update ports.