Ошибка попытка удаления защищенного yum

yum remove libffi-3.0.9-1.el5.rf.i386

Error: Trying to remove "yum", which is protected
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Error: Trying to remove "yum", which is protected
 You could try running: rpm -Va --nofiles --nodigest

2 ответа

Лучший ответ

rpm -e --nodeps PACKAGE

rpm -e --nodeps <package>

Trying to update one of the my VPS today with sudo yum update command and encounter this funky error message :

error: trying to remove «yum», which is protected

From the output :

 --> Finished Dependency Resolution
 Error: Package: coreutils-libs-8.4-31.el6_5.2.x86_64 (@updates)
 Requires: coreutils = 8.4-31.el6_5.2
 Removing: coreutils-8.4-31.el6_5.2.x86_64 (@updates)
 coreutils = 8.4-31.el6_5.2
 Updated By: coreutils-8.4-37.el6.x86_64 (base)
 coreutils = 8.4-37.el6
  You could try using --skip-broken to work around the problem
 ** Found 31 pre-existing rpmdb problem(s), 'yum check' output follows:

and issuing the sudo yum --skip-broken command will work but give this hint for what is causing the funky error :

error: Failed dependencies:

coreutils-libs = 8.4-31.el65.2 is needed by (installed) coreutils-8.4-31.el65.2.x86_64

seems like the package coreutils-8.4-31.el6_5.2.x86_64 is causing the problem with dependencies issue

SOLUTION :

To fix this funky error, use the rpm- e --justdb <package name> command and in my own example here, I’ll just issue

> sudo rpm -e --justdb coreutils-libs-8.4-37.el6.x86_64

and than

> sudo yum update

bingo! all packages updated.

Introduction

I’m in the process of trying to reduce the number of vulnerabilities with an array of projects associated with our Kubernetes cluster, one of the processes involved is hardening our images. To do so, I’m currently utilising Twistlock to highlight all potential vulnerabilities, currently we’re trying to remove all high/important & critical vulnerabilities.

According to Twistlock’s dashboard, one of the packages that’s vulnerable is associated to sqlite & another is associated to libxml2. If I can, I’d also like to remove the vulnerabilities associated with dbus, only at this point I’m a little unsure of how to tackle this.

Process

So far, I’m trying to use a rather primitive process to approach the packages mentioned above, since I’m using CentOS, I’m executing the following commands inside of my dockerfile:

## Use the base image. 
FROM base-img

## Utilise root for package management. 
USER root

RUN yum update
RUN yum clean all 
RUN yum remove sqlite
RUN yum remove libxml2

## Run as non root user.
USER jboss

## Now to remove yum.
RUN rpm -e $(rpm -qa '*yum*')

## etc.

However, this results in some set of errors, like so, when trying to run our docker build command:

...
Error: Trying to remove "systemd", which is protected
Error: Trying to remove "yum", which is protected
...

Conclusion

I believe that I need some assistance form a Linux guru here? Since the requirements of this project is to ensure that the security is kept to a maximum, we’d really like to remove as many potential threats as possible, I’ve pretty much nailed the application layer already. Now I’m delving into the OS layer & soon I’ll be delving into the network layer also, so if anyone can provide any input or guidance on how we could remove such threats, the help would be much appreciated.

Disclaimer

Unfortunately I’m far from a Linux pro, maybe intermediate at best, so please be patient if I’m missing something. I’ve also created a question on SO, only that’s more associated with JBoss, if any of you are able to help with that question, help would be much appreciated there also.

Introduction

I’m in the process of trying to reduce the number of vulnerabilities with an array of projects associated with our Kubernetes cluster, one of the processes involved is hardening our images. To do so, I’m currently utilising Twistlock to highlight all potential vulnerabilities, currently we’re trying to remove all high/important & critical vulnerabilities.

According to Twistlock’s dashboard, one of the packages that’s vulnerable is associated to sqlite & another is associated to libxml2. If I can, I’d also like to remove the vulnerabilities associated with dbus, only at this point I’m a little unsure of how to tackle this.

Process

So far, I’m trying to use a rather primitive process to approach the packages mentioned above, since I’m using CentOS, I’m executing the following commands inside of my dockerfile:

## Use the base image. 
FROM base-img

## Utilise root for package management. 
USER root

RUN yum update
RUN yum clean all 
RUN yum remove sqlite
RUN yum remove libxml2

## Run as non root user.
USER jboss

## Now to remove yum.
RUN rpm -e $(rpm -qa '*yum*')

## etc.

However, this results in some set of errors, like so, when trying to run our docker build command:

...
Error: Trying to remove "systemd", which is protected
Error: Trying to remove "yum", which is protected
...

Conclusion

I believe that I need some assistance form a Linux guru here? Since the requirements of this project is to ensure that the security is kept to a maximum, we’d really like to remove as many potential threats as possible, I’ve pretty much nailed the application layer already. Now I’m delving into the OS layer & soon I’ll be delving into the network layer also, so if anyone can provide any input or guidance on how we could remove such threats, the help would be much appreciated.

Disclaimer

Unfortunately I’m far from a Linux pro, maybe intermediate at best, so please be patient if I’m missing something. I’ve also created a question on SO, only that’s more associated with JBoss, if any of you are able to help with that question, help would be much appreciated there also.