Page 1 of 1

Frustrated with package versioning

Posted: 2020/12/23 15:31:54
by jagauthier
I have an environment that is air-gapped. I deployed 7.8 to it, and I built a local repository.
All my clients use that local repository and life is good.

On an internet connected machine, I built a docker image. This docker image is based on Centos 7.8.
I moved this docker image into my isolated environment to find out the packages that are installed are not the same ones that I have.

In my Dockerfile I disabled updates, so there wasn't a chance of pulling in 7.9 packages.

Code: Select all

RUN yum-config-manager --disable updates
I built the image, and I can immediately see packages are newer than then ones I have.

For instance, this image required java. So, I install "java-1.8.0-openjdk"
Down the line of dependencies I find:
Package mesa-libgbm.x86_64

The package version that I replicated from is 18.3.4-7.el7
Likewise, the version on vault.centos.org is also the same.

However, when yum installs it gets a newer version: 18.3.4-10.el7

Through a little digging, I see that when I browse a mirror, 7.8.2003 isredirects to /7.
This seems to be 7.9. Which is not what I want at all.

I want 7.8 repositories, which is why I started from a 7.8 Docker image.

This is annoying. How do I stay locked into the version I specified instead of this forced update version?

Re: Frustrated with package versioning

Posted: 2020/12/23 17:07:17
by TrevorH
The base repo changes at point release times, not just updates.

Re: Frustrated with package versioning

Posted: 2020/12/23 17:10:35
by jagauthier
How do I stay locked into the version I specified?

Re: Frustrated with package versioning

Posted: 2020/12/23 17:53:56
by TrevorH
You will be missing security updates if you do not move to 7.9. It's not recommended to stay locked on one version.

Re: Frustrated with package versioning

Posted: 2020/12/23 17:58:54
by jagauthier
"I have an environment that is air-gapped."

Security updates are not a concern at this time.

How do I stay locked into the version I specified?

Re: Frustrated with package versioning

Posted: 2020/12/23 19:01:11
by TrevorH
By rsyncing the 7.x.yymm directory, not by using the symlink which always points to the current version. And old releases get archived to vault.centos.org once the next point release comes along.

Re: Frustrated with package versioning

Posted: 2020/12/23 19:13:54
by jlehtone
jagauthier wrote:
2020/12/23 15:31:54
I have an environment that is air-gapped. I deployed 7.8 to it, and I built a local repository.
jagauthier wrote:
2020/12/23 17:58:54
How do I stay locked into the version I specified?
You have local repository. As long as the machines in your bubble use it, they are "locked in".

Re: Frustrated with package versioning

Posted: 2021/01/05 19:19:29
by jagauthier
It seems like everyone who responded did not actually read my post.

Yeah, I have a local repository of a specific version. But I was/am trying to make a docker image using the internet repositories. Those two systems are not connected.

Anyway, I solved it by forcing use of centos vault. It's ugly.

Re: Frustrated with package versioning

Posted: 2021/01/05 19:33:50
by chemal
It's supposed to be ugly, because what you are doing is explicitly unsupported.