hurricanehrndz

Yeah, seems like the container is using a bridge network configuration. If I remember correctly, this is to avoid a conflict with the host network stack in case multiple service try to attain the upnp ports. You can change the configuration by adjusting the containers network configuration to host, of course, at your own peril. It should be a drop down Sent from my ONEPLUS A3000 using Tapatalk

I think you are using the old template v1, you should probably update to the latest.

Reading from the log it seem like ffprobe can not handle ttf files, for some reason you seem to have font files with your media files... which seem to cause emby to crash. Perhaps deleting the ttf files from your media file might solve your issue. PS Issues like this are best posted on emby forums. I am the maintainer and developer of the container and not emby itself, 99% of the issues individuals encounter are actually with the application and not the docker. So it's probably in your best interest to post to the forums supporting the application itself (emby);I suggest this so that users get the best support possible.

There should be an option to increase the number of cores in use in the emby interface. If you post in the emby forums I'm sure some one would answer right away. I can not remember the location off the top of my head Sent from my ONEPLUS A3000 using Tapatalk

The syslog in var log is worth inspecting. If the system crashes after emby if running for a while, than I would heavily suspect the issue to be with either emby or the host (unRAID) Sent from my ONEPLUS A3000 using Tapatalk

I would check unRAID logs. Sounds like your system is having issues Sent from my ONEPLUS A3000 using Tapatalk

I don't see how. Sent from my ONEPLUS A3000 using Tapatalk

The docker itself has been tested and works. Actual issues with emby should be posted on their forums. The devs there including myself will be better able to provide support. Sent from my ONEPLUS A3000 using Tapatalk

Sorry, but this is an isolated issue and issue actually relating to Emby itself. It is probably best that you make a post on the server support subforums of emby's forums. Sent from my ONEPLUS A3000 using Tapatalk

First of all, I'm sorry this has taken me soo long to look into. Second of all I'm wondering if you read the readme? Specifically the the tech details: https://github.com/hurricanehrndz/docker-containers/tree/master/ubooquity#technical-information You will see that you can adjust how much mem java is allowed via an environment variable.

The container update is announced even when the update might be to beta or dev only. You probably are on the latest Sent from my ONEPLUS A3000 using Tapatalk

Cool, the update should work. I do not think there has been any major changes in stable. Sent from my ONEPLUS A3000 using Tapatalk

Stop the docker service all together Sent from my ONEPLUS A3000 using Tapatalk

Your best bet is to fix it at the command line. Use docker commands Sent from my ONEPLUS A3000 using Tapatalk

Sorry, been super busy with work. I'll try my best. It's in the top 5 of my todo Sent from my ONEPLUS A3000 using Tapatalk

Glad to hear it all worked out Sent from my ONEPLUS A3000 using Tapatalk

Don't worry about it. Luke is aware of the issue. Sent from my ONEPLUS A3000 using Tapatalk

Bungee, talk to Luke. He says he knows there is a major issue on beta and dev right now. And hopes to have it fix this evening. Sent from my ONEPLUS A3000 using Tapatalk

Definitely interesting. Please post on the forums with the logs and link it here. I will read into it. Which database improvements. I know someone was working on postgres, but I was not made aware that these changes had been merged. If postres is now the default on beta and dev then that would cause a lot of havoc. Sent from my ONEPLUS A3000 using Tapatalk

Bungee, I know today and tomorrow I will be doing some pretty big changes to the dev and beta containers. Additionally, I know Luke the main developer is making massive changes to Emby as we speak. I do not believe any of the issues you are experiencing are due to the container itself. Since no changes have been made to the container. Instead they are most likely due to the changes being made to Emby itself. I would advise you hit the Emby forums and make a thread under the one of the beta subforums. Sent from my ONEPLUS A3000 using Tapatalk

Additionally once a beta has been updated there is no way of going back. We do not tag images based on version. Sent from my ONEPLUS A3000 using Tapatalk

Ps the repos that became unstable where the the debian based ones. I have not seen this on the suse repos which is what the docker image is based on Sent from my ONEPLUS A3000 using Tapatalk

My post was for the Ubuntu thread. Had nothing to so with the docker thread. If you're looking for stability my recommendation is stay on the stable repo. The beta and dev repo are for testing things out, there will always be a lot changes that will have negative effects on those branches. Sent from my ONEPLUS A3000 using Tapatalk

If you click update, i don't think it will do anything Sent from my ONEPLUS A3000 using Tapatalk

Latest release is 8500 for stable. There's newet builds on the hub but they are beta and dev. Perhaps you should ask the devs of unRAID to filter the update alters by tag. Sent from my ONEPLUS A3000 using Tapatalk