Conversation
| To completely replace the default base repositories during a build the | ||
| option `--force-repo=file:///path/to/repos` can be used. | ||
|
|
||
| When replacing repositories with Katello/Satellite kickstart trees, make sure |
There was a problem hiding this comment.
How does this usually work with Katello/Stellite repos, how are the repos made available to dnf? I'm asking because when we construct the buildroot we just use the dnf from the host, are there any special vars we could pass to dnf to make these entitlements work?
There was a problem hiding this comment.
Kickstart repositories are not subject of HTTP client authentication, Satellite users can just copy and paste them from the UI or CLI. There is no need to get anything from the host.
There was a problem hiding this comment.
I would love if @thozza could also have a quick look at this, I personally lack experience in this (satelite/katello) area. But happy to +1 it as its certainly a very useful hint, I just wonder if it needs more fleshing out of if people familiar with the topic will get enough info from it (I guess they will?)
There was a problem hiding this comment.
I thought about this a bit, and I think that we should instead by default suggest using the --data-dir instead. The main reason is that --force-repo replaces the base repositories for all distributions, while with --data-dir, you could pass different base repos per distro (minor) version.
So while I find documenting a workflow to use Satellite helpful, putting it under --force-repo section is IMHO not the best choice. It would probably warrant for a separate section just about Satellite.
Otherwise, the text looks OK.
mvo5
left a comment
There was a problem hiding this comment.
Approving but my approval is more a +0.5
|
The spellcheck will need to be fixed anyhow before this should merge :) |
|
Rebased, added a note about GPG. |
Building from Satellite repositories is possible via force-repo.