-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues running in Kubernetes #430
Comments
Hi @2o1o0, thanks for the report. I've done all of my testing exclusively in Docker rather than Kubernetes, so I haven't run across this issue. I'll make a change to bind to a higher port. |
@2o1o0 I haven't played with Kubernetes much,, but from what I know with docker you should be able to change the port. I can try to take a looksee |
I've been setting the port with the docker port mapping: But you do have a point that I shouldn't bind to port 80 on the app since some people are deploying the app outside of docker, and it will fail to bind. |
Hey,
Kubernetes let you do a lot of things, if not anything, but that doesnt mean you should do it. To achieve that, you'll need to start escalation privileges, which I'm for sure not granting to an app that doesnt actually require it for specific needs (network, CSI/storage). @michael-j-green thanks for taking a look! |
Listen on any port other than a port less than 1024 |
Describe the bug
Running in Kubernetes is currently an issue as it tries to bind to a port bellow 1024
To Reproduce
Use https://bjw-s.github.io/helm-charts to generate a deployment as I usually do with this kind of projects
Currently using embedded db version to test the app
The app cannot start as it tries to bind it self to port 80
There are a few steps to match K8S hardnening requirements
Expected behavior
I can start the app as a generic K8S app
Additional context
Error :
The text was updated successfully, but these errors were encountered: