Christian Kellner de021b468a stage: use path meta info to run the stage ... Now that the `Stage` contains the `ModuleInfo`, which contains the path the to executable, this can directly be used to execute the stage. To do so, the path to the executable is bind-mounted to a well known path inside the sandbox (`/run/osbuild/bin/$id`) and this is then supplied to the build root as executable to run.		2021-01-18 17:44:46 +01:00
..
formats	stage: add module information about itself	2021-01-18 17:44:46 +01:00
util	util/jsoncomm: chain the BufferError in recv	2020-10-30 17:28:31 +01:00
__init__.py	osbuild: introduce Manifest class	2021-01-09 18:09:47 +01:00
__main__.py	osbuild: always return exit code	2020-10-27 22:04:09 +01:00
api.py	api: ensure parent of socket dir exists	2020-12-04 12:28:30 +01:00
buildroot.py	buildroot: continuously stream log data to monitor	2020-10-28 14:28:07 +01:00
loop.py	loop: use python 3 style base class initialization	2020-10-30 17:28:31 +01:00
main_cli.py	stage: add module information about itself	2021-01-18 17:44:46 +01:00
meta.py	meta: add module path to module info	2021-01-18 17:44:46 +01:00
monitor.py	monitor: add assembler/stage duration	2020-08-06 16:19:47 +02:00
objectstore.py	objectstore: keep strong reference of objects	2021-01-15 13:20:31 +01:00
pipeline.py	stage: use path meta info to run the stage	2021-01-18 17:44:46 +01:00
remoteloop.py	api: remove 'addr' param from message dispatcher	2020-07-29 02:16:20 +01:00
sources.py	api: remove 'addr' param from message dispatcher	2020-07-29 02:16:20 +01:00
treesum.py	treesum: don't use dir_fd parameter in os.scandir()	2019-11-29 00:45:14 +01:00