| 2018-03-21 16:46:25 |
Kyle Fazzari |
description |
Snapd currently contains a number of hooks that are run during installation/refresh, such as the install hook, configure hook, and {pre,post}-refresh hooks. If any of these hooks return non-zero during a refresh, snapd rolls the update back (or aborts the initial install), which is nice, and makes these hooks a good place to run a health check of some kind to ensure the update works. However, doing that only works if what one needs to health check is some sort of headless system service. It doesn't work well for user applications (e.g. skype, slack) because the hooks run as root. |
Snapd currently contains a number of hooks that are run during installation/refresh, such as the install hook, configure hook, and {pre,post}-refresh hooks. If any of these hooks return non-zero during a refresh, snapd rolls the update back (or aborts the initial install), which is nice, and makes these hooks a good place to run a health check of some kind to ensure the update works. However, doing that only works if what one needs to health check is some sort of headless system service. It doesn't work well for user applications (e.g. skype, slack) because the hooks run as root. It also means hooks can never do anything meaningful in $SNAP_USER_{COMMON,DATA}. |
|
