summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorPedro Alvarez <pedro.alvarez@codethink.co.uk>2016-10-17 08:10:28 +0000
committerJavier Jardón <jjardon@gnome.org>2016-11-08 20:00:00 +0000
commit23edf96e3af0812bfa626eb076bc741b0aa54633 (patch)
tree32984728a1ea97ef016adab21d234c0031fb8f95 /scripts
parent3dcb1a2d6f541449ba7d5192c7db9e09204a799b (diff)
downloaddefinitions-3-add-support-for-ostree-deployment.tar.gz
Add ostree.write deployment extension3-add-support-for-ostree-deployment
Reverts commit 36f7e4923ae5d03dd345d74f7fcade48c99a498d This is a simple deployment extension to write the results of a Baserock build to an OSTree repo. See ostree.write.help for more information. The Baserock reference systems contain static device nodes, which are not supported by OSTree, and are obsolete on Linux systems. To work around this problem, I added a strip-device-nodes.configure extension. The systems should still work the same as devtmpfs will create the device nodes. I've tested this by deploying minimal-system-x86_64 to an OSTree repo, then checking it out into a temporary directory, creating a read-only bind-mount of the temporary directory and chrooting then into it. This is only going to be useful for containers systems and chroots for the time being. We would need to make some quite major changes to the Baserock reference systems to enable deployment to VMs or bare metal using OSTree. Change-Id: Ic393bdec7b28341fc5dfa56bb684217d964be5ff
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions