I’m on the struggle bus here, getting the same result trying to deploy the helm chart from the helm/stable repository and the drone repository (the newer chart) with the same result. Has anyone else run into this or have an idea where to look? I have entered the server info for my Github enterprise server, put in all other git level variables and this is always the result. I set enable persistent volume to false so I take out any DB issues.
This message occurs when something external to Drone sends a SIGTERM or SIGINT to Drone (for example, if you run docker stop). This tells me Kubernetes (or someone on the host OS) is stopping your Drone instance. Since this is happening outside of Drone and is not within Drone’s control, I cannot say what would be causing this.
It looks like something is killing Drone as soon as it starts. The reason you are seeing different logs when enabling / disabling cron is because it changes the initialization steps. In both instances Drone is being killed, but at different points in the initialization process which yields slightly different logs. But in either case, as Brad suggests, it looks like Drone is being killed.
the error, which comes from the Go standard library, is throwing a permission denied error when binding to :80. Since this error comes from the Go standard library it would lead me to believe there must be some permission error. Perhaps the port is already in use?
Have you considered engaging Rancher support? The error message (permission denied when binding to the port) does not seem like a Drone problem to me, but a problem with the runtime environment and / or its security settings.
The bind permission denied issue was coming from the Rancher project( a rancher construct that groups namespaces) I am using that didn’t have a default pod security policy set. In Rancher, you can set default PSP’s at the cluster level, which was set to restricted (blocks port 80 from binding). A pod security policy of unrestricted was set in the project ( and thus inherited in my namespace) which resolved the issue. Thank you @ashwilliams1 and @bradrydzewski for the help. Hopefully someone else running this in rancher will find this useful at some point.