Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iocage upgrade failing due to wrong plugin_repository address #6

Open
artas360 opened this issue Aug 12, 2022 · 3 comments
Open

iocage upgrade failing due to wrong plugin_repository address #6

artas360 opened this issue Aug 12, 2022 · 3 comments

Comments

@artas360
Copy link

Issue:

Updating the emby-server jail though iocage upgrade is failing because the property plugin_repository in the config.json is set to the official iocage repo instead of this one.

Solution:
To fix this, set manually the correct address by running

iocage set plugin_repository='https://github.com/MediaBrowser/iocage-amd64.git' emby-server

I did not figure out a way set the property correctly during the iocage fetch, which would be cleaner...

It might be useful to add this step to the documentation page https://emby.media/truenas-server.html since there are a couple of threads in the emby forum from users having issues with their upgrades. Is there a way to create a PR for this page?

@alucryd
Copy link
Collaborator

alucryd commented Aug 14, 2022

Can't find another way to achieve that either. We'll add that to our instructions, thanks for the heads up!

@LukePulverenti
Copy link
Member

LukePulverenti commented Aug 16, 2022

@artas360 do you know if this line will need to vary based on the truenas 12 and 13 branches? They use the same github repo, just different branches of it. Thanks.

@LukePulverenti
Copy link
Member

Worst case scenario we can always split our iocage repo into two and create new ones as needed for newer truenas versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants