microdnf can not access custom Satellite repositories

Solution In Progress - Updated -


  • I am building a container image based on rhel-atomic and when running microdnf /etc/yum.repos.d/redhat.repo is generated and I can enable and install packages from different rhel-7-repositories.
    However, on the host OS, there are several other repositories in the redhat.repo-file, including the epel-repository. Why are these repositories not included in the generated redhat.repo-file in the image?
  • If we use as base image rhel7 and use yum to install, we can properly use all repos that are subscribed to the host that runs docker build, both rhel repos and repos with our applications/dependencies. If we use base rhel7-atomic and try to enable our repos, it says repository not found.


  • Red Hat Satellite 6.x
  • microdnf

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content