Conversation
|
Note that the CI failure does not appear to be a consequence of this PR. |
|
can you provide more details why you would change the port inside the container? usually one would change the host port mapping. changing the DRONE_SERVER_PORT is generally not required or recommended. Also, this probably won't work as intended because |
So the Drone server pod can be run as non-root. At the moment, it does look like the server and the kube runner work fine non-root, although the build container spawned by the runner currently assumes root.
That's no problem, the PR takes this into account. |
| {{ $envKey | upper }}: {{ $envVal | quote }} | ||
| {{- end }} | ||
| {{- if .Values.port }} | ||
| DRONE_SERVER_PORT: :{{ .Values.port }} |
|
Hi @jtackaberry I run into the same problem, when running the drone server in OpenShift. Your solution also may lead into having the DRONE_SERVER_PORT variable twice in the configmap if it is also defined as env variable. |
|
Putting a plus-one here as well. Getting drone to run with out root is a goal for us, and it requires the chart to switch to a different port. At the moment we have to use a very permissive PSP to get drone to run, and we'd prefer not to. |
|
Apologies for the extreme delay on this. Since this PR, the server chart has changed a bit. I think this is a mistake, we should support changing the port. I am a little hesitant to automatically set |
This PR adds a
portvalue to the Helm chart. The primary use case is to enable binding to high ports to avoid running Drone server as root.