Open endersonmaia opened 1 month ago
When the docker build fails the machine creation should not happen. If all the user wants is to build the Dockerfile he can use docker build and not use sunodo at all.
When the docker build fails the machine creation should not happen.
In the use case I described, the docker build is OK.
If all the user wants is to build the Dockerfile he can use docker build and not use sunodo at all.
In the use case I described, I want to run sunodo shell
, and for that I need the .sunodo/image.ext2
, that's created by sunodo build
before the snapshot.
📚 Context
When testing the creation a cartesi-machine and desired dependencies, a developer may need several
sunodo build
andsunodo shell
iterations and the snapshot step can take some time.✔️ Solution
Add a
--skip-machine-snapshot
tosunodo build
command so that this step is not done at the end, and the develop can still runsunodo shell
to assess the rootfs generated that will be used by the snapshot step.📈 Subtasks
--skip-machine-snapshot
tosunodo build
command