Is there a thing where you can give it a container image, some machine requirements, some input files (maybe in an object store), the output files you want it to capture, the location to put things (maybe a presigned object/prefix url) and it takes care of running the thing and saving the outputs?
It would produce an execution receipt for the computation and seems like something that might be nice to standardize. I know container engines like podman save exit code and logs in a local database, but not outputs. Would also want to capture some info about the execution environment like provider, machine type/stats, etc.
Maybe the saving part could be a poststop hook? Not sure on output format; some things would be small and could be inline with the receipt, others could be a few large files going to individual objects, others a tar/squash of a whole dir from the container.
0 comments
—
Ask HN: Is there a container runner with data capture? OCI "receipt"? · HackerTrans
It would produce an execution receipt for the computation and seems like something that might be nice to standardize. I know container engines like podman save exit code and logs in a local database, but not outputs. Would also want to capture some info about the execution environment like provider, machine type/stats, etc.
Maybe the saving part could be a poststop hook? Not sure on output format; some things would be small and could be inline with the receipt, others could be a few large files going to individual objects, others a tar/squash of a whole dir from the container.