PowerProtect: Falha na inicialização dos contêineres do Docker do Cyber Recovery (Não é possível se conectar ao daemon do Docker)

Summary: O cliente não consegue usar o Cyber Recovery porque os contêineres do docker não podem ser iniciados porque o daemon do docker não está em execução.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Ao tentar executar o Docker PS, uma mensagem é exibida perguntando se o daemon do Docker está em execução.
  
[root@hostname ~]# docker ps -a
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?


O serviço Docker não está ativo
  
[root@hostname ~]# systemctl status docker
? docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Wed 2022-11-16 07:39:05 EST; 3min 34s ago
     Docs: https://docs.docker.com
 Main PID: 7590 (code=exited, status=1/FAILURE)

Nov 16 07:39:02 hostname systemd[1]: docker.service failed.
Nov 16 07:39:05 hostname systemd[1]: docker.service holdoff time over, scheduling restart.
Nov 16 07:39:05 hostname systemd[1]: Stopped Docker Application Container Engine.
Nov 16 07:39:05 hostname systemd[1]: start request repeated too quickly for docker.service
Nov 16 07:39:05 hostname systemd[1]: Failed to start Docker Application Container Engine.
Nov 16 07:39:05 hostname systemd[1]: Unit docker.service entered failed state.
Nov 16 07:39:05 hostname systemd[1]: docker.service failed.
Nov 16 07:39:40 hostname systemd[1]: start request repeated too quickly for docker.service
Nov 16 07:39:40 hostname systemd[1]: Failed to start Docker Application Container Engine.
Nov 16 07:39:40 hostname systemd[1]: docker.service failed.


Cause

Ao tentar iniciar o daemon do Docker, há uma mensagem alertando sobre um problema de espaço
  
[root@ hostname]# sudo dockerd
Error starting daemon: Unable to get the TempDir under /var/lib/docker: mkdir /var/lib/docker/tmp: no space left on device

Houve um problema de espaço em disco. O file system raiz parece estar cheio:
  
[root@hostname ~]# df -kh
Filesystem                                Size  Used Avail Use% Mounted on
/dev/mapper/centos_hostname-root   38G   38G   20K 100% /        <<<<
devtmpfs                                  1.9G     0  1.9G   0% /dev
tmpfs                                     1.9G  8.0K  1.9G   1% /dev/shm
tmpfs                                     1.9G  8.9M  1.9G   1% /run
tmpfs                                     1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/sda1                                1014M  189M  826M  19% /boot
/dev/mapper/centos_ehs--hostname-home   19G  3.0G   16G  17% /home
tmpfs                                     379M     0  379M   0% /run/user/0
[root@hostname ~]#



Resolution

Depois de recuperar algum espaço, removendo alguns pacotes de suporte antigos e pacotes de versões anteriores que não são mais necessários, reinicialize a VM do Cyber Recovery. Os contêineres estavam em execução novamente e o cliente pôde retomar o uso do Cyber Recovery.

Affected Products

Cyber Recovery Series

Products

Cyber Recovery Series, CyberSense
Article Properties
Article Number: 000214296
Article Type: Solution
Last Modified: 04 Nov 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.