FN11.3 iocage jails - Plex, Tautulli, Sonarr, Radarr, Lidarr, Jackett, Transmission, Organizr

[intelligence]

Noticed that stuff downloaded via Sonarr/Radarr takes up twice the size, i.e. files are copied, not hardlinked, anyone experiencing the same issue? Any body with a fix?

https://forums.freenas.org/index.php?threads/iocage-hard-link-issues-with-radarr-and-sonarr.62356/

 

[Chris Moore]

(not that good with hardware)

Ask for help. There are people who are happy to help.

Sent from my SAMSUNG-SGH-I537 using Tapatalk

 

[diskdiddler]

Hi,

I finally want to start making some iocage jails in anticipation of 11.2.
I'm looking at the resources guide, if I'm reading it right, most of the commands in this guide we run in the shell of the main host OS, right?
I'm just a tiny bit concerned, I recall reading to be extremely careful in there, so I try to know what I'm doing first.

Based on the commands, it's 99.9% obvious to me, the commands are pushing into iocage except this first one

"

Code:

echo '{"pkgs":["mono","curl","ca_root_nss"]}' > /tmp/pkg.json

"

What's this doing? I assume it's some kind of downloading of a package, storing it in the temp folder, for iocage to use later?

 

[danb35]

What's this doing?

It's creating a list, in JSON format, of packages to be installed when the jail is created (the -p /tmp/pkg.json part of the iocage create command). Saves the step of installing the packages after the jail is created.

 

[diskdiddler]

I figured it was something innocuous but they say you should never type a command you don't understand into a console.

I'll play under my VM for a few days first.
(I've realised in the past week or so, that I'm still going to need 'manual jails' and not just convenient plugins, as some of the jails I use, the Freshport simply isn't maintained often enough, so I'm going to need iocage skills)


Thanks Dan.

 

[mow4cash]

This think this line needs to be fixed

Code:

iocage exec jackett "tar -xzvf Jackett.Binaries.Mono.tar.gz -C /usr/local/share"   to
iocage exec jackett "tar -xzvf /usr/local/share/Jackett.Binaries.Mono.tar.gz -C /usr/local/share"

Jackett needs to use the latest repo to meet the mono dependency and I assume radarr and sonarr should use the latest also.

Thanks for the guide it has been a huge help.

 

[Pentaflake]

This think this line needs to be fixed

Code:

iocage exec jackett "tar -xzvf Jackett.Binaries.Mono.tar.gz -C /usr/local/share"   to
iocage exec jackett "tar -xzvf /usr/local/share/Jackett.Binaries.Mono.tar.gz -C /usr/local/share"

Jackett needs to use the latest repo to meet the mono dependency and I assume radarr and sonarr should use the latest also.

Thanks for the guide it has been a huge help.

I've made the correction. I had it right on my notes but wrong on here. I am waiting to actually add an update to this thread as last month the version of mono on the latest repo was updated to 5.10.1.47 and it added BoringSSL support to allow for TLS1.2. As soon as 5.10.1.47_3 hits the
latest repository we should be in business again with Sonarr/Radarr/Lidarr/Jackett for automatic updates again as it properly enables BoringSSL in the build process.

 

[diskdiddler]

EDIT: Dupe, see below

 

[diskdiddler]

The guide is outright broken / incorrect for jackett, on both FN 11.1 U5 and FN nightlies.

step #1, works fine

step #2, works, kinda, it does spit out a DNS error, both nightly and U5

Code:

iocage create -n "jackett" -p /tmp/pkg.json -r 11.1-RELEASE ip4_addr="vnet0|<192.168.0.121>/<255.255.255.0>" defaultrouter="<192.168.0.254>" vnet="on" allow_raw_sockets="1" boot="on"

jackett successfully created!
Testing SRV response to FreeBSD
Error: error sending query: General LDNS error
{repo} could not be reached, please check your DNS

step #4, has hardcoded stuff which makes no sense?

Code:

iocage fstab -a jackett /mnt/tank1/apps/jackett /config nullfs rw 0 0

I've changed /tank1/ to the following

/iocage/
/POOLNAMEHERE/ (obviously, my pool name)
Neither of these work.

I'm guessing the jackett section needs a bit of work (sorry guys, thanks regardless)

 

[mow4cash]

The guide is outright broken / incorrect for jackett, on both FN 11.1 U5 and FN nightlies.

step #1, works fine

step #2, works, kinda, it does spit out a DNS error, both nightly and U5

Code:

iocage create -n "jackett" -p /tmp/pkg.json -r 11.1-RELEASE ip4_addr="vnet0|<192.168.0.121>/<255.255.255.0>" defaultrouter="<192.168.0.254>" vnet="on" allow_raw_sockets="1" boot="on"

step #4, has hardcoded stuff which makes no sense?

Code:

iocage fstab -a jackett /mnt/tank1/apps/jackett /config nullfs rw 0 0

I've changed /tank1/ to the following

/iocage/
/POOLNAMEHERE/ (obviously, my pool name)
Neither of these work.

I'm guessing the jackett section needs a bit of work (sorry guys, thanks regardless)

I get the DNS error also when using a .json. I opened a ticket but it was closed because it could not be reproduced even though others have reported the same thing. Maybe opening another ticket will get someone to dig a little deeper.

The jackett code worked fine for me.

 

[Wim Mistiaen]

What is the current recomendation? Go ahead and install jails with iocage, or wait untill 11.2 is released?

 

[diskdiddler]

What is the current recomendation? Go ahead and install jails with iocage, or wait untill 11.2 is released?

Based on the failure rate of this guide, I'd hold and wait

 

[diskdiddler]

I get the DNS error also when using a .json. I opened a ticket but it was closed because it could not be reproduced even though others have reported the same thing. Maybe opening another ticket will get someone to dig a little deeper.

The jackett code worked fine for me.

When you say opened a ticket? I thought this guide was community driven and not supported?


I'm glad to open a job but it feels very lazy and unfair to me? Surely it's just the commands we're following are incorrect and there is a correct set of guidelines to get this working? I doubt is the fault of the os.


Claiming it's not able to be reproduced is ridiculous though, I did it in 60 seconds on my VM snapshots.

Anyone else got Jackett working from this guide?

 

[chrisada]

Sszz

What is the current recomendation? Go ahead and install jails with iocage, or wait untill 11.2 is released?

If

Sent from my Pixel 2 XL using Tapatalk

 

[danb35]

When you say opened a ticket?

This guide is a community resource, but FreeNAS itself isn't. If networking doesn't work on a newly-created jail (which has been the case for the last several releases), that's probably a bug, and opening a ticket would be appropriate if it hasn't already been reported.

 

[mow4cash]

What is the current recomendation? Go ahead and install jails with iocage, or wait untill 11.2 is released?

Make them now. The jails themselves shouldn't change if 11.2 is released.

 

[mow4cash]

When you say opened a ticket? I thought this guide was community driven and not supported?


I'm glad to open a job but it feels very lazy and unfair to me? Surely it's just the commands we're following are incorrect and there is a correct set of guidelines to get this working? I doubt is the fault of the os.


Claiming it's not able to be reproduced is ridiculous though, I did it in 60 seconds on my VM snapshots.

Anyone else got Jackett working from this guide?

Jackett worked for me but I also pulled from the jackett pre release repo.

The code is correct, however he was unable to reproduce. If you want to take the time to figure out what could be different with our configurations as apposed to his, go for it and open a ticket so they can fix it. They can't fix it if they can't reproduce.

It's a guide not a copy and paste. Things change. Releases change, links change, dependencies and so on.

 

[anmnz]

step #2, works, kinda, it does spit out a DNS error, both nightly and U5

Code:

iocage create -n "jackett" -p /tmp/pkg.json -r 11.1-RELEASE ip4_addr="vnet0|<192.168.0.121>/<255.255.255.0>" defaultrouter="<192.168.0.254>" vnet="on" allow_raw_sockets="1" boot="on"

You seem to have angle brackets around the IP addresses in this command? That's wrong. Those arguments should look more like this:

Code:

ip4_addr="vnet0|192.168.0.121/24" defaultrouter="192.168.0.254"

 

[diskdiddler]

This guide is a community resource, but FreeNAS itself isn't. If networking doesn't work on a newly-created jail (which has been the case for the last several releases), that's probably a bug, and opening a ticket would be appropriate if it hasn't already been reported.

Ok, but I'm pretty dense, how do I know it's not just the iocage command I pasted in from the CLI which is lacking a DNS section? (I guess I'm asking, is this a bug or is the command bunk?) - check the resources guide and look at the jackett section.


EDIT:

I have manually configured DNS on my VM and fixed the commands as per the post below, the DNS error (small, I admit) is still occurring.

Code:

Error: error sending query: General LDNS error								 
{repo} could not be reached, please check your DNS   

 

[diskdiddler]

You seem to have angle brackets around the IP addresses in this command? That's wrong. Those arguments should look more like this:

Code:

ip4_addr="vnet0|192.168.0.121/24" defaultrouter="192.168.0.254"

I think the guide shouldn't say

"blah blah <ip> blah blah"

It should say

"blah blah <ip> blah blah"