Skip to content

CentOS 7 EOL affecting docker build #17894

@sklochkov2

Description

@sklochkov2

Bug Report

Due to CentOS 7 being EOL and the repos being taken down, docker image fails to build from scratch (see the error message below) due to unavailable base repository. If it would help, I may create a PR to migrate Dockerfile to Rocky Linux 8 or 9.

What version of TiKV are you using?

I tried building the docker image for various versions from scratch

What operating system and CPU are you using?

Ubuntu 24.04 / Ryzen 5950X on my development workstation.

Steps to reproduce

  1. Clone the tikv repo.
  2. Follow the CONTRIBUING.md doc on installing dependencies.
  3. Run make docker

What did you expect?

The docker image would be built

What did happened?

Step 7/44 : RUN yum install -y epel-release &&     yum clean all &&     yum makecache
 ---> Running in b14cff9a0424
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64

Metadata

Metadata

Assignees

Labels

type/enhancementThe issue or PR belongs to an enhancement.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions