[mythtv-users] Centos 7 and mythtv
Stephen Collier
stephenbcollier at gmail.com
Sun Aug 21 23:02:14 UTC 2016
I've been building 0.28 el6 and el7 for several months via an automated
mock process and atrpms original specs.
its up to version 19 of 0.28
scrpms.net/pub/RPMS
Cheers
Stephen
On 21/08/2016 2:00 AM, Rob Verduijn wrote:
>
>
> 2016-08-20 15:45 GMT+02:00 Mike Perkins <mikep at randomtraveller.org.uk
> <mailto:mikep at randomtraveller.org.uk>>:
>
> On 20/08/16 13:21, Rob Verduijn wrote:
>
>
> Hi,
>
> I've also been running mythtv on centos 7 for some time now.
> When 0.28 was released I was a bit miffed because there was no
> repo that
> contained the rpm's available.
> Also the qt5 requirement was a bit of a challenge.
>
> I solved it by installing mythtv into a fedora 28 docker
> container on the
> centos 7.2 host.
>
> This solved a lot of problems for me.
> * quite a lot of rpms that in my view should not be instaled
> on a server
> have been removed since they are installed in the container
> (cleaner server
> config)
> * it's now in an isolated container again which makes a far
> better security
> solution than running it directly on a server backend
> * it's a lot easier to allow a container access to a pci-card
> then to share
> it via passthrough to a vm ( most pci cards can't deal with
> this including
> mine)
> * Rebuilding a docker container with a docker file when there
> are updates
> is really easy.
> * the mariadb runs in a dedicated mariadb container.
> * cronjobs are started on the centos host with the 'container
> exec' command
> which runs them as the mythuser in the mythtvbackend container.
>
> There are also drawbacks.
> * running mythtv setup is a pain but not impossible (I created
> a dedicated
> container for this that I only build when needed which is
> almost never)
> * database schema updates are a challenge too (waiting for
> lock ends with a
> fail),
> for now I did a temporary mariadb install on my frontend to
> deal with
> this (import old db from backend, upgrade, export new db to
> backend)
> I removed it once this was done. I'm still pondering what
> the best
> solution is for this (I'm tinking of merging it with the mythsetup
> container)
> * it creates a rather large container
> * I still need to create a container for the mythweb interface
> * Ofcourse this is complete f#@$-up of the container
> principle, but it
> works for me :-) (and was a nice learing experience)
>
> Any chance you can write this up and add it to the wiki? I always
> thought that containers were essentially VMs but from what you say
> above this isn't exactly so.
>
> Alternative methods for building and/or using a mythtv system are
> always of interest, especially if it can lead to more efficient
> use of hardware.
>
> --
>
> Mike Perkins
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> <http://lists.mythtv.org/mailman/listinfo/mythtv-users>
> http://wiki.mythtv.org/Mailing_List_etiquette
> <http://wiki.mythtv.org/Mailing_List_etiquette>
> MythTV Forums: https://forum.mythtv.org
>
>
> I really do not like editing wiki's
> But since I've been using mythtv for over a decade I think it's a fair
> suggestion.
> However, Like I said my container solution still needs work.
> So it will be a work in progress for some time.
>
> Cheers
> Rob Verduijn
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160822/d482ed28/attachment.html>
More information about the mythtv-users
mailing list