sonicaj

@Saberwolf64 we allow mounting host paths inside the app. Apart from that ensuring that the docker image has support for specific features, i am sorry we wouldn't be ensuring that...

@zacbrown i am closing this issue in light of the comments above, please feel free to create a suggestion ticket at https://ixsystems.atlassian.net if you think we are missing some aspect....

That would be awesome ; ) > > If I get ambitious, I may submit a patch that specializes root_dir and server for old FreeBSD releases in a similar way...

@djmixman can you please verify if this is still an issue for you ? ``` root@freenas[~]# iocage list Creating vol1/iocage/jails +-----+------+-------+---------+-----+ | JID | NAME | STATE | RELEASE |...

Perfect, thank you

@ohmantics can you please create an issue at https://jira.ixsystems.com ? And please attach a debug of the system as well ( System -> Advanced ). Thank you

@fulder I think it breaks existing implementation where maintainers would expect release version of TN to be followed. Also ideally TN freebsd version and plugin release freebsd version should be...

> I'm thinking something like this (where branch is optional) > > ``` > { > "name": "awesome-plugin", > "release": "12.2-RELEASE", > "artifact": "http://github/whatever-plugin.git, > "branch": "1.0", > "official": "false"....

> The remnants of this legacy behavior lurks in eldritch obscurity. Those who dare to comprehend its incomprehensible logic fall into a deep state of despair. As I delved into...

Thanks!