CFT - Apps bound to specific IPs

Apps and Virtualization
1

Folks,

As part of the run-up to Fangtooth in a couple months, we’ve enabled a handful of apps which can now select IPs to bind to directly. These are visible on the EE side, so we’d appreciate some testing of them and feedback.

The apps that have been updated are:

  • adguard-home
  • calibre-web
  • esphome
  • handbrake-web
  • homearr
  • invoiceninja
  • it-tools
  • jelu
  • lyrion-music-server
  • minecraft-bedrock
  • portainer
  • romm
  • sastifactory-server
  • steam-headless
  • tererria
  • tiaji
  • umami
  • urbackup
  • zigbee2mqtt
  • stable/emby

Before anybody asks, the reason we can’t enable this across the board yet, is that it will break existing upgrades of those apps which are previously installed until the system is upgraded to Fangtooth.

However, in the meantime, we’d love some testing and feedback to ensure the functionality is working properly.

2

Hmmm, I am already running portainer, as an experiment. Most of my containers are in Portainer, in a SCALE-Jail using nspawn, precisley and only because that has a different IP address

When I edit the existing portainer - there is nothing about IP addresses, so I am guessing that I cannot “retrofit” an existing container and will need to delete and recreate which isn’t an issue as I don’t actually use the IX Portainer yet.

A new container does have the IP address option.

3

I’m going to go out on a limb here, and show my ignorance: exactly where am I supposed to select an ip to bind to?

(I’ve installed Jelu and it’s running, but I can’t see anything different between Jelu and another app from the app catalogue which isn’t on the post #1 list. The documentation search didn’t bring anything up.)

4

You may have to click to “refresh catalog” first, but when you do, on the install page for those apps you will see the following:

image

1 Like
5

Thanks!

6

So, with these apps, is it expected that the IP Binding will work in EE?

7

Yes, for the apps we just enabled them in. However, only on a fresh install, upgrade will not work of those apps. For that to work we need FT to go out the door. This is just early testing of a handful so we can work out kinks along with the FT beta in next couple weeks.

1 Like
8

Neat.

Now we just need a docker network picker UI to be added to the apps :wink:

1 Like
9

Steam Headless crashes on a loop constantly for me. I haven’t been able to get it to work in a separate container since 4.10.0.2 which I believe had newer nvidia drivers. Not sure why they were rolled back from 550.135 to 550.127.05

Also wasn’t the separation of the GPU drivers from the OS supposed to allow us to update the drivers?

10

This seems like a topic for a new General thread with full hardware and problem description.

1 Like
11

CFT?
CORE Finally Terminated?
:scream:

12

No, self updating the drivers out of band wasn’t part of that design. Original intent was to eventually let us ship different sets of drivers, I.E. the current NVIDIA drivers, Legacy Driver, etc. But allowing random updates of them is out of scope at this point.

13

“Call For Testing”, but now that you’ve called it that, I will never unsee it :joy:

14

Thanks for the update. Any word on why drivers were rolled back?

15

Which drivers were rolled back? You’ll need to be specific. Current driver in 24.10.2 is 550.142