From 143be69ed4d2353349f5b7030c3bb1ce1a166a99 Mon Sep 17 00:00:00 2001 From: Fiete Ostkamp Date: Mon, 23 Sep 2024 07:50:26 +0200 Subject: Update README - add missing instructions for binding to privileged ports - use node 18 in docker build Issue-ID: PORTALNG-118 Change-Id: Ib4360f920d96c6ccef40bf50c5f815488c1ddfd2 Signed-off-by: Fiete Ostkamp --- Dockerfile | 2 +- README.md | 9 +++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index 1b5205b..4eb1cbb 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,6 +1,6 @@ # the JRE is required by the openapi-generator-cli # FROM eclipse-temurin:17-jre-alpine as builder -FROM node:16-alpine AS builder +FROM node:18-alpine AS builder RUN apk update && \ apk add openjdk17 WORKDIR /usr/src/app diff --git a/README.md b/README.md index 40e0084..0d49135 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,15 @@ ## Getting started The portal-ng ui can either be developed against a remote cluster or it's dependencies can be run locally on your machine. +### Allow unpriviliged (non-sudo) programs to bind to low ports (i.e 80) + +On linux, programs that run in an unprivileged mode are not allowed to bind to low ports (<=1024). +A capability needs to be defined to allow the `node` process to do so: + +```sh +sudo setcap 'cap_net_bind_service=+ep' `readlink -f \`which node\`` +``` + ### Developing against a remote cluster To develop against a remote cluster, the webpack proxy needs to be configured to forward requests to the remote cluster urls. For that we are providing a `staging.proxy.config.json.template` file that needs to be adjusted with your cluster hostnames and then saved as `staging.proxy.config.json`. -- cgit 1.2.3-korg