summaryrefslogtreecommitdiff
path: root/morphlib/app.py
diff options
context:
space:
mode:
authorAdam Coldrick <adam.coldrick@codethink.co.uk>2015-01-28 15:53:27 +0000
committerAdam Coldrick <adam.coldrick@codethink.co.uk>2015-02-06 12:57:49 +0000
commit3f7e38a7f2721a404ebbfb130b51fa639a9e7360 (patch)
tree94ce5fd63b3364dba0b0e9c00b63cac4094e4aa7 /morphlib/app.py
parent1701ee47ee9261ce52d8509f1fff1ad8a4e3134b (diff)
downloadmorph-3f7e38a7f2721a404ebbfb130b51fa639a9e7360.tar.gz
Use overlayfs when deploying
When deploying, configuration extensions are run against the unpacked tarball of a system created by a build. If we are to use OSTree to store systems (rather than tarballs) this will not be possible as the result of `ostree checkout` would be read-only. To solve this, we use overlayfs to mount the unpacked tarball underneath a temporary directory somewhere, and run the configuration extensions on that mount point. This means that the changes are made in the temporary directory rather than directly on the tarball.
Diffstat (limited to 'morphlib/app.py')
0 files changed, 0 insertions, 0 deletions