Sunday, 29 March 2020

RHEL/CentOS 8 docker-ce installation Error: package docker-ce-3:19.03.8-3.el7.x86_64 requires containerd.io >= 1.2.2-3

If you are facing the error while installing docker-ce as follow:




To fix it, you can either install a specific stable version like:

$ sudo dnf install docker-ce-3:18.09.1-3.el7


OR
 

you can force the installation of docker-ce with the --nobest option


$ sudo dnf install --nobest docker-ce

OR


Install the latest available containerd.io package manually


$ sudo dnf install 
https://download.docker.com/linux/centos/7/x86_64/stable/Packages/containerd.io-1.2.6-3.3.el7.x86_64.rpm

After the package is installed, we can simply install the latest docker-ce


$ sudo dnf install docker-ce

This option is less convenient since the containerd.io package is not installed 
as a dependency of docker-ce, therefore it will not be removed automatically when 
the latter is uninstalled from the system.


I hope it will fix your issue!!


Thanks!!!!!!! Enjoy Programming :)

Reference Links
===================================

https://linuxconfig.org/how-to-install-docker-in-rhel-8


Saturday, 28 March 2020

RHEL/CentOS 8 Error: problem with installed package podman-docker

If you guys are facing an error while installing Docker CE on Centos/RHEL 8 as follow:




Here is the workaround For CentOS/RHEL:


Uninstall podman before updating it sudo yum -y remove podman and install it back w/o manpages:
# install all podman dependencies except podman-manpages
sudo yum -y install oci-systemd-hook libvarlink
Then again install docker-ce

# install docker-ce
sudo yum -y install docker-ce
It should work this time!

If still facing an issue, try to use --nobest flag with command


$ sudo dnf -y  install docker-ce --nobest

Workaround for For Ubunutu:

sudo apt install -o Dpkg::Options::="--force-overwrite" podman


Thanks!!! Enjoy Programming :)


Reference Links:
=============================

https://github.com/containers/libpod/issues/4791#issuecomment-575124857


Monday, 16 March 2020

RabbitMQ server issue - vhost ‘/’ is down




I'm using RabbitMQ with Celery(Django) for the last couple of months now but recently we faced an unexpected issue where RabbitMQ is not accepting tasks in its queues and error in logs say:

INTERNAL_ERROR — aess to prod_vhost ‘/’ refused for user ‘prod’: prod_vhost ‘/’ is down.`

Now, how to solve this problem:

From the Rabbitmq log file you can get the destination file URL, in my case it was


/var/lib/rabbitmq/mnesia/rabbit@hostname_1/msg_stores/prod_vhost/784WB90CIFDYO9LJI6DKMI78L/recovery.d ets”

If you have problem with vhost '/', most probably the file url will be

/var/lib/rabbitmq/mnesia/rabbit@hostname_1/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/recovery.d ets”


Resolution :
  1. Stop 'rabbitmq-server'.
  2. delete the folder that contains the corrupt files. In this case: 784WB90CIFDYO9LJI6DKMI78L
  3. Start 'rabbitmq-server'. It should work fine now.


 
Thanks!!! Enjoy Programming!!!!!!! :)


Reference Link:


Elasticsearch: Copy Index Structure