Hi,
I’m using Nexus3 in private cloud environment, and I configured yum group repository and yum proxy repository. Yum-proxy repository is a member of yum-group repository.
In VM of private cloud, I made repofile of repository.
This is the repofile example. The repofile is looking at yum group repository.
and yum-proxy repository remote storage is Index of /vault/rocky/
The maximum and minimum component age of yum-proxy is 1440.
I thought yum-proxy repository and yum-group repository have same file tree, but it’s different.
More specifically, yum-proxy file tree have a recent public rockylinux repository but yum-group doesn’t.
Here is the yum-proxy repodata file tree and yum-group repodata file tree. [yum-proxy Appstream]
3d1c00f07858e1d997effa767f1f40a4e8771fd42ebd274e0df44ade752f7076-modules.yaml.xz
9b154248aab29dc4212e432a00ce96504c2f383e4340fd80799f9a85be5eb4e0-updateinfo.xml.gz
d480b24465d4202202039c23e7dea847f193ec71ce1fecf4ab8d40842ae88705-primary.xml.gz
e7a0fb6fea3b38fea65a0e6d06c17bc5921584a26358416f689af7eb56cef2f0-other.xml.gz
ec2fa1982439f4b0ca7dc86f882f18657457a2d42f06ac6718298c7f7528df43-comps-AppStream.x86_64.xml
f19203db21be0e35ee7882ae95e9ff4a36cd4cfc287168dbbbf3218e4e0e85b3-filelists.xml.gz
repomd.xml
The maximum and minimum component age of yum-proxy is 1440.
That setting determines how often the proxy repository will look for updated metadata. Try lowering it, or manually clear the cache by pressing “expire cache” in the proxy repository settings.
Also note that the file names in the proxy repository will be different than the ones in the remote. The metadata in the proxy is rewritten so that URL’s in it will refer to the proxy repository.
Thanks for your answer.
But my question is the proxy repository have normal repomd.xml but the yum group repositroy that have proxy repository as a member have unnormal repomd.xml.
The yum group repository only have one member.(proxy repository)
I know that yum group repository role is just grouping various repositories by one url.
I can’t understand why yum group repository and yum proxy repository(member of group repo) have different repomd.xml.
Below is each of repomd.xml.
<?xml version="1.0" encoding="UTF-8"?>
<repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke.edu/metadata/rpm">
**<revision>1706058605</revision>** // the revision is also strange.
The difference in revision itself is okay, but the problem is that yum group repository repomd.xml doesn’t have a module data type, so if I use yum group for private repo, the installation of module package is failed.
The reason why I need module data type is when I try to install docker in rocky 8.8 (using private repo), below error is occured.
+ sh -c 'yum install -y -q docker-ce-20.10.7-3.el8'
No available modular metadata for modular package 'container-selinux-2:2.205.0-2.module+el8.8.0+1265+fa25dd7a.noarch', it cannot be installed on the system
No available modular metadata for modular package 'fuse-overlayfs-1.11-1.module+el8.8.0+1265+fa25dd7a.x86_64', it cannot be installed on the system
No available modular metadata for modular package 'libslirp-4.4.0-1.module+el8.8.0+1266+6052254c.x86_64', it cannot be installed on the system
No available modular metadata for modular package 'slirp4netns-1.2.0-2.module+el8.8.0+1265+fa25dd7a.x86_64', it cannot be installed on the system
Error: No available modular metadata for modular package
That’s because in Yum group repository there is no modular repodata.
$ dnf module list
Last metadata expiration check: 0:19:46 ago on Mon 22 Jan 2024 11:09:33 PM UTC.
@modulefailsafe
and This is my yum proxy repo setting and yum group repo setting yum proxy
name : yum-rocky-proxy
remote storage : Index of /vault/rocky/
the other settings are default.
yum group
online status
Group - member repositories : yum-rocky-proxy
and This is the whole contents of repodata.md of Yum proxy repo and Yum group repo.
The folder tree is same. yum proxy repo