saw the new eel update and tried again.
after update, my dashboard was a mess. but after edit everything seems ok.
for jailmaker i delete old one and create new one. the nvidia card settings in the jailmaker config breaks jailmaker from working. so i disable that and it worked after that.
then i got jailmaker and docker in it running. i did a jlmkr list and it shows the 192.168.0.24 i use for the docker
then i deployed dockge docker compose, so that is running.
- normal usage of truenas for nas purposes work
- jailmaker works
- docker in jailmaker is running
earlier the url wouldnt work 192.168.0.24:5001
*yes i tried using private browser to make sure its clean but that didnt work
hours later i tried again and it worked
*screenshot as proof
So now i will procede to deploy the rest of my containers docker compose saved in the stack folder.
So successfully recovered after migrating from dragonfish to eel for jailmaker with docker running in it.
The networking for it might still be flaky (for me). Will continue to monitor if it’s the case or not.
But i did delete old jailmaker and redid that from scratch.
What i did not do from scratch was the networking, but maybe i should. But i can’t recall the exact steps i did x-x; scared i can’t enter truenas if i botch that up thats why i hadn’t done that yet.
This was the step to doing it
the sfp+ fiber connection is correctly being shown in truenas. this was the update in case there was confusion. It was simply a matter off editting the dashboard to choose to show it. Because prior it didn’t show it for some reason after updating to eel from dragonfish.
But it remains true that i keep losing access to my container everytime i try access via 192.168.0.24:5001 *this is for dockge as an example
but i deleted and redid and hopefully that problem goes away will see
*update
figured out the problem. it had nothing to do with truenas. it was my own misconfiguration in router in regards to networking for docker not working most of the time
my bad