Better command execution in Docker about runme HOT 1 OPEN

If a Docker image does not exist, runme will build it
Does this imply i) docker is running locally? ii) images are stored locally?

What if I build my images in the Cloud (e.g. Cloud Build) and store them in GCR?

When all commands will be executed, the container will be shut down.

Does this inhibit the case where container lifecycle needs to be managed outside of RunMe? Can RunMe treat docker as a special case of remote execution where it knows how to manage the lifecycle of the container and does it for you?

How would other remote targets be specified? In your proposal, it seems like in your runme.yaml you can only specify local execution via docker. If you want to support remote would you want to specify a gRPC address? Can the target executor only be specified at the document level or can different cells run in different executors?

from runme.