I just installed the latest app for Mariadb which has the assign-ip-to-app feature that’s new. I added the target IP to the truenas server first, jumped through all the test and save config hoops, so it’s available to the app.
The rest of the app config was all fill in the blanks, and in the network section I set the IP by choosing the new aliased IP from a dropdown list. Saved it, and it pulled the image and tried to come up. However, it cannot start. I keep the shell info on in the Truenas interface at the bottom and see it talking about some network magic it’s trying to implement and the app dies. It will never start in its current state. The IP is available, it’s not a duplicate on the network, and I even set up DNS so I could ping it by hostname once it was working. It does ping, so Truenas has accepted the alias.
Any other Fangtooth users wanna run through this exercise, or any app devs working on upgrading the apps want to look into this? It’s kinda dead in the water. Haven’t tried just letting it borrow the host’s IP and use a port like all the other docker stuff and I don’t intend to use it that way.
If it manages to pull the image before erroring out during container set up, there is a chance that what you’re looking at here isn’t actually a network issue. Lets try ruling out any permissions issues first by (test) installing the app using ixvolume datasets instead of host paths and these network settings.
In stock form, only filling out user, password, database, and root pw, it installed the app and launches fine. It’s running. Next I’ll edit the IP address to bind to the alias and see if it breaks.
Edit: IP alias worked. Now to really break it and add the host volumes again. They’re just datasets but permissions may be wrong…even if I hit “create dataset” to give them somewhere to live, I assumed the app handled perms if it had to create the subfolder or whatever. Worked with the other 10 apps so far.
In order to redefine storage I had to tear it all down and start over. Bound IP alias, set acl on host dataset, and bang! One more barrier to my Core migration smashed. Thanks for making it easy. Also confused as to why this is the first time I ever ran into this issue…kinda wish something would have nudged me this direction.
