Siumauricio
commented
3 weeks ago In order to terminate the build of any type of source it is not possible to implement because internally we use queues with redis which is used with bullmq to precisely prevent the server from freezing, and they do not offer a functionality to stop or terminate the running process unless you pay for a paid version. https://github.com/taskforcesh/bullmq/issues/632
An alternative to prevent your server from freezing in case you have very limited resources is to build the image on a ci/cd and push it to a docker registry and in dokploy simply download and run the image so you don't do the heavy process of building the image.
DenisVASI9
What problem will this feature address?
This feature will address the issue that arises when there are errors in the Dockerfile, causing the container to fail to start correctly due to incorrect commands. Currently, the service does not provide the ability to stop the container startup process before it completes, which can lead to the system hanging or being unable to properly handle the error.
Describe the solution you'd like
I would like to have the ability to interrupt the container startup process if it hasn't completed yet, similar to how you can stop a running container. This could be implemented in the container management interface by adding an option to "Terminate Startup," allowing the user to manually interrupt the process.
Describe alternatives you've considered
As a temporary workaround, I manually changed the container status from "Running" to "Done" in the database, which allowed me to terminate the startup process. However, this solution is inconvenient and unintuitive for most users. A simpler and more obvious method integrated into the interface would be much more useful and user-friendly.
Additional context
No response