You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run an enclave, the docker image is built and the service starts off of it.
Ideally, if I make a change to the underlying code the docker image containerizes, I can leverage enclave edits to only restart the service with the rebuilt image.
However, right now this isn't detected by our interpreter so rerunning the package will not detect an update on add_service and not rerun the service, as desired.
How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.
What area of the product does this pertain to?
Other: anything not covered by the above
The text was updated successfully, but these errors were encountered:
Background & motivation
Right now if you use an ImageBuildSpec like so:
Desired behaviour
If you run an enclave, the docker image is built and the service starts off of it.
Ideally, if I make a change to the underlying code the docker image containerizes, I can leverage enclave edits to only restart the service with the rebuilt image.
However, right now this isn't detected by our interpreter so rerunning the package will not detect an update on
add_service
and not rerun the service, as desired.How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.
What area of the product does this pertain to?
Other: anything not covered by the above
The text was updated successfully, but these errors were encountered: