summaryrefslogtreecommitdiff
path: root/without-test-modules
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-04-14 16:32:45 +0000
commite43c1aba0fe2e1513033731fa833472c399dd600 (patch)
treedc96bf22b64cf8cc6d1b0b962124e4af3cdcadec /without-test-modules
parent2c9804e5ca217970d8b6d00670773051b141dded (diff)
downloadmorph-e43c1aba0fe2e1513033731fa833472c399dd600.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. Change-Id: Iafcb78feaa1d6d37be4f52420c03d5b96d5c81ee
Diffstat (limited to 'without-test-modules')
0 files changed, 0 insertions, 0 deletions