davidchisnall / act-pot Goto Github PK

Upgrading packages or the base in the runner image is currently a manual process, which does not scale. You should be able to define a flavour for all of your custom configuration (done) and then recreate a pot extracting the configuration that was generated the first time a runner was registered.

This probably depends on bsdpot/pot#162 for a clean mechanism. It might be possible to just copy the files out of the ZFS mount, but that depends on implementation details of pot (and configurations, since pot doesn't provide a mechanism for describing where it is mounting everything and currently mounts them in a very surprising place, so is likely to be changed by users (/opt is supposed to be for things installed from source, not things managed by tools).