Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I've got to believe this is a common problem, but can't seem to find a solution. We have some 600 server VM's (all running CentOS 6.x) in a private network that we need to administer, none of which have internet access, nor can have, so using yum is out. Occasionally we need to add packages to these machines that lead to dependency hell. Try to install this-new-thing.x86_64.rpm but you can't because it needs a dependency that's not there, so you find the dependency but it needs more dependencies, and so on down a deep rabbit hole.
I figure there's got to be something out there that let's me try to install an rpm in a local machine with internet access without actually installing it on the host machine, pulls the dependency tree for that rpm and all it's dependency rpms into a package or sandboxed file/dir so I can collect everything, maybe even make it into one big rpm? and move the finished product up to our server environment where I can then install without dependency snags.
If there's nothing like that out there, how do other admin's get around a problem like this?
Set up a local mirror of the yum repos. Only allow this machine Internet access (or just use the DVD/ISO images and forgo Internet entirely). Point the VMs (they DO have inTRAnet access, right?) at this yum repo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.