Linux - ContainersThis forum is for the discussion of all topics relating to Linux containers. Docker, LXC, LXD, runC, containerd, CoreOS, Kubernetes, Mesos, rkt, and all other Linux container platforms are welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It appears that the script may be tied to the explicit Ubuntu operating system as opposed to being for a container. Have you asked on the MythTV forums for a similar maintenance script that would be useful in a container?
Never considered that. I assumed it knew it was an Ubuntu container and that was that. I just did a post on Mythtv forums. Will report back.
I would check the /etc/os-release file on both systems (full install and container) and compare. Also, compare the output of "uname -a" on both. You will likely see differences that may be behind why the script gets installed on the full install but not the container.
The only thing that made me think along these lines is because it appears that the script is doing myth updates as well as possibly OS updates, and knowing the distro is key to ensuring that the updates are scripted correctly.
Both os-release & uname -a are the same output. I checked lsb-release (installed in container after your initial response) and it is identical to the host. Even rebuilt the container intalling it first, then the second install command did the mythtv-backend.
Quote:
It appears that the script may be tied to the explicit Ubuntu operating system as opposed to being for a container.
The script I'm mainly looking for is supposedly just for cleaning up the database. It's a perl script.
Marking solved. Why the libdbi-perl and libmythtv-perl packages weren't pulled automatically I cannot say. I had to manually get the script from their git. I hope it's not against any rules to say I won't bother going there again. I can't even post their own file names to my thread. As such I couldn't show them my dockerfile or anything. Waste of time
This is a working Dockerfile for a basic mythtv-backend. Including link to my git for the other files as needed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.