Hello everyone! First time user of Balena here :smiley: I have setup a Ktor application and deployed it on an RPi-4. I have a Docker image that I am building locally by extending balenalib/raspberrypi3-openjdk:8-jdk since there is no JDK one for RPi-4 that I have found. The application is deployed…

Hi there, just to rewind a bit on the conversation, what is the reason for you needing to modify the iptables? In Docker you can map the hostOS port to a container port, so you can do something like 80:8080, and run your web application on port 8080. Is this a multicontainer application? You can see…

Hey, can you share the docker file so we can have a better sense of what might be the issue.

Sure, here it is: https://gist.github.com/pavlospt/bf6e78d4759d58b8471281b2addbe162 Dockerfile FROM balenalib/raspberrypi3-openjdk:8-jdk ENV APPLICATION_USER ktor RUN useradd -ms /bin/bash $APPLICATION_USER RUN mkdir /app RUN chown -R $APPLICATION_USER /app USER $APPLICATION_USER This f…

Can you please try as well iptables -P FORWARD ACCEPT as something like that is often needed when running under balenaOS compared to other distributions which have less restrictive default forward policy and see whether this will solve the issue for you?

This rule alone does not work. I used as well: iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080 But I still get the issue with the repeated redirects, because the load balancer cannot distinguish the proper headers.

I am not using Docker Compose right now. Do you believe it would be easier if I would change the setup to docker-compose?

If it is a single container, you can just start your server on port 80 and it should work as expected. See the docs for more information: https://www.balena.io/docs/learn/develop/runtime/#single-container-applications

[image] pavlospt: since you can not listen on port 80 due to Linux permissions for ports lower than 1024, which makes Netty crash with permission denied. Netty does not accept it if I start it on port 80 by default and that is why I was searching for a different approach!

I see, in that case you can just add a docker-compose file with a single service and map the ports there.

Will try that as well. Is there a way to revert the iptables rules though in order to be sure, that the docker compose rule works due to port exposure?

Hello, iptables rules should not persist across reboots, so it should be sufficient to restart the device to return to a clean state

Load balancer/reverse-proxy redirects on Ktor application for public URL

Product support balenaOS

nazrhom April 3, 2020, 11:44am 20

Glad to hear you managed to get it sorted. Good luck, happy to help if anything else pops up

Balena CLI - docker-compose context takes into account .gitignore on deploy

Topic		Replies	Views
Single URL over application of several devices Product support	6	429	April 8, 2020
NAT or IP Port forwarding from container balenaOS	9	1794	December 5, 2022
Help exposing container port balenaOS support , raspberrypi3 , network	13	2356	November 25, 2019
Enable Public Device URL but not IP Address Access Product support	18	2461	February 13, 2019
Expose port other than 80 to device public URL Product support	6	1800	October 15, 2020

Load balancer/reverse-proxy redirects on Ktor application for public URL

Related topics