Hey there!
A little question for you :)
I'd like to setup my truenas scale keeping both truecharts applications and the possibility to deploy stack directly with portainer.
My target is to be able to deploy portainer stacks and containers with dedicated ip addresses on the same subnet of my host (to reach directly them without any kind of port forwarding).
What I did untill now is:
- in tuenas: setup a bridge with my primary nic providing the ip address to the bridge interface
- deploy a docker-compose app with a static dedicated ip (show expert config -> Host interface: bridge nic created before)
- bind mount 2 datasets (ex. /docker-data:/data , /docker-lib:/var/lib/docker) in docker-compose app
- in the "docker-compose" app - use portainer docker-compose.yaml file and deploy it with docker-compose up
- in portainer: setup a macvlan interface and bind it to every container deployed through portainer
Do you think that the whole thing would work even after truenas upgrades?
In your opinion am I missing something related to volume persistance etc?
If you have any suggestion to avoid this scenario and achive the same result - I would be glad to hear new ideas ;)
Thanks
Ric
A little question for you :)
I'd like to setup my truenas scale keeping both truecharts applications and the possibility to deploy stack directly with portainer.
My target is to be able to deploy portainer stacks and containers with dedicated ip addresses on the same subnet of my host (to reach directly them without any kind of port forwarding).
What I did untill now is:
- in tuenas: setup a bridge with my primary nic providing the ip address to the bridge interface
- deploy a docker-compose app with a static dedicated ip (show expert config -> Host interface: bridge nic created before)
- bind mount 2 datasets (ex. /docker-data:/data , /docker-lib:/var/lib/docker) in docker-compose app
- in the "docker-compose" app - use portainer docker-compose.yaml file and deploy it with docker-compose up
- in portainer: setup a macvlan interface and bind it to every container deployed through portainer
Do you think that the whole thing would work even after truenas upgrades?
In your opinion am I missing something related to volume persistance etc?
If you have any suggestion to avoid this scenario and achive the same result - I would be glad to hear new ideas ;)
Thanks
Ric
