Not sure either how “double management” would play out.
The safe choice is likely to install Portainer from TrueNAS catalog, and then install and manage further containers from Portainer.
Is not the traffic then router through your main interface?
That was what I found out, trying to achieve that I have a Custom App in TrueNAS Scale which would be utilizing a subnet on my network which is strictly through VPN.
I have tagged VLANs coming in to an interface on my baremetal TrueNAS Scale installation (enp4s0), and I have configured this Custom App for qBittorrent:
services:
qbittorrent:
container_name: qbittorrent
image: qbittorrentofficial/qbittorrent-nox:latest
hostname: qbittorrent
environment:
- QBT_LEGAL_NOTICE=confirm
- QBT_VERSION=latest
- PUID=850
- PGID=1002
- TZ=Europe/Paris
- TORRENTING_PORT=6881
- QBT_WEBUI_PORT=8090
volumes:
- /mnt/Tank/Docker/qbittorrent:/config
- /mnt/Tank/Torrents:/downloads
ports:
- 8090:8090/tcp
- 6881:6881/tcp
- 6881:6881/udp
restart: unless-stopped
stop_grace_period: 30m
tmpfs:
- /tmp
tty: true
networks:
vlan60_macvlan:
ipv4_address: 192.168.60.30 # <-- Choose an unused IP from your subnet
dns:
- 192.168.60.24 # <-- DNS
networks:
vlan60_macvlan:
driver: macvlan
driver_opts:
parent: enp4s0.60 # <-- match your parent interface name
ipam:
config:
- subnet: 192.168.60.0/24 # <-- match your LAN subnet
gateway: 192.168.60.2 # <-- match your router gateway
My greatest fear is creating a feature request on the forums, but not getting any votes.
My second greatest fear is creating a feature request on the forums, getting a record-breaking number of votes, popping a bottle of champagne to celebrate, and then this happens.
Stay strong, @victor. I will inject another batch of votes from my bot army to help you out.
Thanks a bunch! I was struggling to figure out how to get my pi-hole to point to my nginx proxy manager for multiple hours and this was the comment that finally got it all working.
Wait, wasn’t this already accepted?
Or is the devil in the details, this feature request asks for it to be changed in EE, but the planned change is coming in Fangtooth?
Apps with Configurable IP addresses: Apps in Electric Eel use TrueNAS’s host IP address. Fangtooth enables IP alias addresses to be created and assigned to one or more Apps.
This was accepted:
It’s a simpler thing to provide which accomplishes much of what’s desired.
The key difference is “allow app to have its own ip” vs “allow app to bind to a specific ip alias on the host”
Ideally, TrueNAS should also support creating, utilizing macvlan ips with apps, which is more or less what this request is for.