Closed kolia closed 3 years ago
I thought the original point of using devspace was to keep the data on the pod in sync with your local environment over the lifespan of the pod. Is that not the case?
If it isn't the case we should just drop it and use kubectl cp
instead
The Julia_pod script keeps running as long as the pod is up, and the devspace processes are cleaned up after the pod is done. (The kubectl attach is blocking until the attached Julia process exits.)
Previous
trap
didn't seem to work, leaving behind running (mostly harmless)devspace
processes on exit.This was causing
julia_pod
to hang on exit when run from a juliarun(pipeline(julia_pod))
context.