yo/gocage
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Update README

Browse Source
This commit is contained in:
yo 2024-09-22 19:30:43 +02:00
parent c79ac4ac30
commit 5d4c54f5fa
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -137,20 +137,36 @@ Stop jails
---------- ----------
`gocage stop test` `gocage stop test`
Update jails Update jails
---------- ----------
To update jail patch version, use gocage update : To update jail patch version, use gocage update :
`gocage update test` `gocage update test`
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 :
`gocage update -d fastgocage -r 14.1-RELEASE`
Upgrade jails Upgrade jails
---------- ----------
To upgrade jail to newer release, use gocage upgrade : To upgrade jail to newer release, use gocage upgrade :
`gocage upgrade -r 13.2-RELEASE test` `gocage upgrade -r 13.2-RELEASE test`
A pre-upgrade snapshot wil be made so we can rollback if needed. A pre-upgrade snapshot wil be made so you can rollback if needed.
Upgrading basejail/release
----------
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
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`
You can now update ports.
Delete jails Delete jails
---------- ----------