Closed rberrelleza closed 2 years ago
@pchico83 this is something that was going to get fixed with the latest okteto binary, right?
The alternative fix is that the docker extension API enabled a way to kill the launched process...
Could be call 'okteto destroy' directly?
@pchico83 wdty? Calling okteto destroy
but with the -f
to identify it? is this an option?
My other concern is when they leave the extension, we've seen that the extension gets restarted and there are no destructors or handlers on their API, which will leave the process hanging too...
The next okteto cli version will take care of killing the previous execution of okteto up
, so you can go back in the extension and run again with no issue. I would go with that for now, destroying everything would make the next execution much slower
Also, I created an issue in the docker extension SDK to support the cancelation of a running command
Just to properly track this, the issue that will allow the CLI to kill previous execution is being tracked here: https://github.com/okteto/okteto/issues/2294, right @pchico83 ?
@rlamana right
So with https://github.com/okteto/okteto/issues/2294 the experience at least is fixed and launching it again won't fail. I'll remove this issue from the april-15th
release.
When I click stop, okteto is not stopped. If I then launch the same compose again, it fails to start because the port is taken.