opensource/rkt
1
0
Fork 0
mirror of https://github.com/rkt/rkt.git synced 2026-03-13 09:40:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

Documentation: add upgrading doc

Browse Source
This commit is contained in:
Iago López Galeiras
2017-11-08 15:11:52 +01:00
parent a1a97d417e
commit bc2397c729
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/upgrading.md Normal file
View File

@@ -0,0 +1,13 @@
## Upgrading rkt
Usually, upgrading rkt should work without doing anything special: pods started with the old version will continue running and new pods will be started with the new version.
However, in some cases special care must be taken.
### When the rkt api-service is running
If the api-service is running and the new version of rkt does a store version upgrade that requires migration, new invocations of rkt will be blocked.
This is so because the api-service is a long running process that holds a lock on the store, and the store migration needs to take an exclusive lock on it.
For this reason, it is recommended to stop the api-service and start the latest version when upgrading rkt.
This recommendation doesn't apply if the new api-service is listening on a different port and using a different [rkt data directory](commands.md#global-options) via the `--dir` flag.