Thanks for the input. What you suggests does work, but the minute you change any setting and ‘save’ it defaults back to 6881, which I imagine is a bug in QB resetting the port number. I seem to recall something similar a while back before it was fixed.
Essentially if you set (say 44344) on the container, it tries to connect on 6881 on first start up regardless. I can see this when adding a seeding torrent and a certain site tracker reports a 6881 connection (which they block). Change the port in the settings to 44344 and save, and the tracker will then correctly report 44344, even though the settings still show 6881. All well and good. Now if you change any setting, regardless, through the settings panel and save, the port changes back to 6881.
Long story short, you can workaround by always re-inputting the port (if different from 6881), everytime you go into QB settings and make a save. As long as you do this, the new port setting will persist even after bashing the container. The minute you change any setting though and dont re-input the port, it will revert.
I’m leaving my findings here, just because I’ve been banging my head against this problem for a day or so, thinking I must be doing something wrong. Hopefully it might save someone a similar headache, until its fixed in QB. I’ll raise a bug on QB git with this info.